Update ZISHGUX.m #2

ksbhaskar · 2015-01-29T20:35:26Z

Add entyref DEL1. Here is a test case for the added code:

kbhaskar@bhaskark:$ touch /tmp/tmp ; ls -l /tmp/tmp
-rw-r--r-- 1 kbhaskar gtc 0 Jan 29 15:33 /tmp/tmp
kbhaskar@bhaskark:$ /usr/lib/fis-gtm/V6.2-001_x86_64/gtm -run ^%XCMD 'ZPRINT DEL1^test1:DEL1+3'
DEL1(%F) ; Delete one file
O %F
C %F:(DELETE:DESTROY)
Q
kbhaskar@bhaskark:$ /usr/lib/fis-gtm/V6.2-001_x86_64/gtm -run ^%XCMD 'D DEL1^test1("/tmp/tmp")'
kbhaskar@bhaskark:$ ls -l /tmp/tmp
ls: cannot access /tmp/tmp: No such file or directory
kbhaskar@bhaskark:~$

Add entyref DEL1. Here is a test case for the added code: kbhaskar@bhaskark:~$ touch /tmp/tmp ; ls -l /tmp/tmp -rw-r--r-- 1 kbhaskar gtc 0 Jan 29 15:33 /tmp/tmp kbhaskar@bhaskark:~$ /usr/lib/fis-gtm/V6.2-001_x86_64/gtm -run ^%XCMD 'ZPRINT DEL1^test1:DEL1+3' DEL1(%F) ; Delete one file O %F C %F:(DELETE:DESTROY) Q kbhaskar@bhaskark:~$ /usr/lib/fis-gtm/V6.2-001_x86_64/gtm -run ^%XCMD 'D DEL1^test1("/tmp/tmp")' kbhaskar@bhaskark:~$ ls -l /tmp/tmp ls: cannot access /tmp/tmp: No such file or directory kbhaskar@bhaskark:~$

Patch Subject: Patients on Specific Drug Rpt, WS Issue & PRN IV labels Description: ============ This patch will resolve the following issues: 1) Erroneous data on Patient on Specific Drug Report 2) Ward Stock issue with Clinic Orders 3) IV order of PRN is printing multiple labels Associated Remedy ticket(s): ============================ 1)INC000000941177 Erroneous data on Patient on Specific Drug Report Duplicate: INC000001029951 Patient on Specific Drug Report issue 2)INC000000970007 Ward Stock issue with Clinic Orders 3)INC000000741106 IV order of PRN is printing multiple labels Associated NSR(s): ================== N/A Participating Test Sites: ========================= Upstate New York VAMC (Batavia, Buffalo, Canandaigua, Syracuse, Bath, Albany) West Palm Beach VAMC Augusta - Charlie Norwood VA Medical Center Remedy Overview: ================ Issue 1: -------- INC000000941177 Erroneous data on Patient on Specific Report Problem: -------- The Patient on Specific Drug report, when run with a date range of today thru tomorrow, is displaying a patient who died several months ago and the order it is displaying does not fall within the date range specified. Resolution: ----------- A modification is made to the AUD cross-reference of the PHARMACY PATIENT file (#55). A post-install routine was created to check the "AUD" x-ref in the PHARMACY PATIENT file (#55) for STOP DATE/TIMEs that contain quotes around them and fix them by removing the quotes. Data Dictionary: ---------------- BEFORE: 55.06,34 STOP DATE/TIME 2;4 DATE (Required) INPUT TRANSFORM: X:X=+X&X&$D(^PS(55,DA(1),5,DA,2)) "S PSGDL=X D EN2^PSSDDUT3" S %DT="ERTX" D ^%DT S X=+Y K:Y'>0 X LAST EDITED: JUN 25, 2013 HELP-PROMPT: Enter the date and time that the last dose is to be given (and the order will expire). DESCRIPTION: This is the date and time the order will automatically expire. This package initially calculates a default stop date, depending on the SITE PARAMETERS. EXECUTABLE HELP: D EN^DDIOL(" TIME IS REQUIRED.","","?0") GROUP: PSJU NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER CROSS-REFERENCE: 55.06^ASD^MUMPS 1)= S ^PS(55,DA(1),5,"AUS",+X,DA)="" I $P($G(^P S(55,DA(1),5,DA,0)),"^",7)]"" S ^PS(55,DA(1),5, "AU",$P(^(0),"^",7),+X,DA)="" 2)= K ^PS(55,DA(1),5,"AUS",+X,DA) I $P($G(^PS(5 5,DA(1),5,DA,0)),"^",7)]"" K ^PS(55,DA(1),5,"AU ",$P(^(0),"^",7),+X,DA) 3)= NEEDED BY UNIT DOSE Used by Unit Dose to gather orders. X-refs are in the form of: ^PS(55,DA(1),"AU",status,stop date/time,DA) ^PS(55,DA(1),"AUS",stop date/time,DA) These are used primarily by the profiles. CROSS-REFERENCE: 55.06^AL53^MUMPS 1)= I '$D(DIU(0)) D:$D(PSGAL(53))WorldVistA#2 KILL^PSGAL5 :PSGAL(53)=X K PSGAL 2)= I '$D(DIU(0)),'$D(PSGPO) S PSGAL(53)=X,PSGA L("C")=6000,PSGALFF=34 D ^PSGAL5 3)= UNIT DOSE ACTIVITY LOG Used by Unit Dose to log any changes made to this field. CROSS-REFERENCE: 55^AUD 1)= S ^PS(55,"AUD",$E(X,1,30),DA(1),DA)="" 2)= K ^PS(55,"AUD",$E(X,1,30),DA(1),DA) Identifies verified Unit Dose orders by the order's stop date/time. RECORD INDEXES: ACRUD (#450) (WHOLE FILE #55), AUDC (#483) (WHOLE FILE #55), AUN (#485), CIMOU (#1131) (WHOLE FILE #55) AFTER: 55.06,34 STOP DATE/TIME 2;4 DATE (Required) INPUT TRANSFORM: X:X=+X&X&$D(^PS(55,DA(1),5,DA,2)) "S PSGDL=X D EN2^PSSDDUT3" S %DT="ERTX" D ^%DT S X=+Y K:Y'>0 X LAST EDITED: JUN 25, 2013 HELP-PROMPT: Enter the date and time that the last dose is to be given (and the order will expire). DESCRIPTION: This is the date and time the order will automatically expire. This package initially calculates a default stop date, depending on the SITE PARAMETERS. EXECUTABLE HELP: D EN^DDIOL(" TIME IS REQUIRED.","","?0") GROUP: PSJU NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER TRIGGERED by the PREVIOUS STOP DATE/TIME field of the UNIT DOSE sub-field of the PHARMACY PATIENT File CROSS-REFERENCE: 55.06^ASD^MUMPS 1)= S ^PS(55,DA(1),5,"AUS",+X,DA)="" I $P($G(^P S(55,DA(1),5,DA,0)),"^",7)]"" S ^PS(55,DA(1),5, "AU",$P(^(0),"^",7),+X,DA)="" 2)= K ^PS(55,DA(1),5,"AUS",+X,DA) I $P($G(^PS(5 5,DA(1),5,DA,0)),"^",7)]"" K ^PS(55,DA(1),5,"AU ",$P(^(0),"^",7),+X,DA) 3)= NEEDED BY UNIT DOSE Used by Unit Dose to gather orders. X-refs are in the form of: ^PS(55,DA(1),"AU",status,stop date/time,DA) ^PS(55,DA(1),"AUS",stop date/time,DA) These are used primarily by the profiles. CROSS-REFERENCE: 55.06^AL53^MUMPS 1)= I '$D(DIU(0)) D:$D(PSGAL(53))WorldVistA#2 KILL^PSGAL5 :PSGAL(53)=X K PSGAL 2)= I '$D(DIU(0)),'$D(PSGPO) S PSGAL(53)=X,PSGA L("C")=6000,PSGALFF=34 D ^PSGAL5 3)= UNIT DOSE ACTIVITY LOG Used by Unit Dose to log any changes made to this field. CROSS-REFERENCE: 55^AUD 1)= S ^PS(55,"AUD",+(X),DA(1),DA)="" 2)= K ^PS(55,"AUD",+(X),DA(1),DA) Identifies verified Unit Dose orders by the order's stop date/time. RECORD INDEX: ACRUD (#470) MUMPS IR ACTION WHOLE FILE (#55) Short Descr: Clinical Reminders index. Description: This cross-reference builds two indexes, one for finding all patients with a particular drug and one for finding all the drugs a patient has. The indexes are stored in the Clinical Reminders index global as: ^PXRMINDX(55,"IP",DRUG,DFN,START,STOP,DAS) ^PXRMINDX(55,"PI",DFN,DRUG,START,STOP,DAS) respectively. START is the start date and STOP is the stop date. For all the details, see the Clinical Reminders Index Technical Guide/Programmer's Manual. Set Logic: D SPSPA^PSJXRFS(.X,.DA,"UD") Set Cond: S X=$$PATCH^XPDUTL("PXRM*1.5*12") Kill Logic: D KPSPA^PSJXRFK(.X,.DA,"UD") Kill Cond: S X=$$PATCH^XPDUTL("PXRM*1.5*12") Whole Kill: K ^PXRMINDX(55) X(1): START DATE/TIME (55.06,10) (Subscr 1) (forwards) X(2): STOP DATE/TIME (55.06,34) (Subscr 2) (forwards) RECORD INDEX: AUDC (#501) REGULAR IR SORTING ONLY WHOLE FILE (#55) Short Descr: List of patients with orders associated with clinic appointments. Set Logic: S ^PS(55,"AUDC",$E(X(1),1,20),$E(X(2),1,20),DA( 1),DA)="" Kill Logic: K ^PS(55,"AUDC",$E(X(1),1,20),$E(X(2),1,20),DA( 1),DA) Whole Kill: K ^PS(55,"AUDC") X(1): STOP DATE/TIME (55.06,34) (Subscr 1) (Len 20) (forwards) X(2): CLINIC (55.06,130) (Subscr 2) (Len 20) (forwards) RECORD INDEX: AUN (#503) REGULAR IR SORTING ONLY Short Descr: Clinic cross-reference. Description: This cross-reference is used to easily determine if a specific patient has clinic orders. Set Logic: S ^PS(55,DA(1),5,"AUN",X(1),X(2),DA)="" Kill Logic: K ^PS(55,DA(1),5,"AUN",X(1),X(2),DA) Whole Kill: K ^PS(55,DA(1),5,"AUN") X(1): STOP DATE/TIME (55.06,34) (Subscr 1) (forwards) X(2): CLINIC (55.06,130) (Subscr 2) (forwards) RECORD INDEX: CIMOU (#744) REGULAR IR LOOKUP & SORTING WHOLE FILE (#55) Short Descr: CIMOU - PS(55,"CIMOU",PATIENT,CLINIC,STOP DATE/TIME,PATIENT,ORDER) Description: This cross reference is used during enhanced order checks for quick access to clinic order information for unit dose orders by PATIENT, CLINIC, STOP DATE/TIME and ORDER NUMBER. The set condition checks to see if the clinic is defined with YES answered for the ADMINISTER INPATIENT MEDS parameter under the SET UP A CLINIC [SDBUILD] option and if the order has an appointment date/time defined. If both are true, the cross reference is defined. Using the same criteria, this cross reference will be defined if a clinic is added or edited using the CLINIC DEFINITION [PSJ CD] option. Set Logic: S ^PS(55,"CIMOU",X(1),X(2),X(3),DA(1),DA)="" Set Cond: S X=$$CHECK^PSJIMO1() I X Kill Logic: K ^PS(55,"CIMOU",X(1),X(2),X(3),DA(1),DA) Whole Kill: K ^PS(55,"CIMOU") X(1): PATIENT NAME (55.06,.5) (Subscr 1) (forwards) X(2): CLINIC (55.06,130) (Subscr 2) (forwards) X(3): STOP DATE/TIME (55.06,34) (Subscr 3) (forwards) Issue 2: -------- INC000000970007 Ward Stock issue with Clinic Orders Problem: -------- Clinic orders for Unit Dose (UD) are determining Ward Stock ("WS") (for profile display) based on the location of the LAST admission. So if it's an outpatient, and they were last admitted to a location that has a lot of items stocked, you see "WS" in the last column of the Inpatient Profile. Also with new UD orders, if the Dispense Drug is WS, it displays that message before prompting for pre-exchange doses (just like normal Inpatient functionality if it's WS). Resolution: ----------- A modification was made to the PUD tag in routine PSJLMPRU to not display WS on the Inpatient Profile screen for Clinic Orders. A modification was also made to the EN tag of routine PSGPEN to ensure that the message for ward stock item does not display when verifying a Clinic Order. Issue 3: -------- Problem: -------- When an IV order created in CPRS, with a schedule that contains a frequency changed to a PRN order in Vista, the Frequency is not cleared out and is stored in the PHARMACY PATIENT file #55. The release of PSJ*5.0*194 fixed the issue of multiple labels but not the carry over of the Frequency. Resolution: ----------- A modification was made to the SET55 tag in routine PSIVORFB to check to see if the schedule contains PRN (as needed), and if so, do not store a frequency in the PHARMACY PATIENT file (#55). Other Components ================ AUD cross-reference for PHARMACY PATIENT file (#55) Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/b0ced814/Packages/Inpatient+Medications/Patches/PSJ_5.0_323

Patch Subject: MASTER VETERAN INDEX VISTA ENHANCEMENTS - ITERATION 15 Description: ============ ************************************************************************* * This patch may be installed with users on the system, however because * * the patient lookup routines are being exported with this patch, we * * strongly advise that it be installed after business hours. * ************************************************************************* DG*5.3*915 is the only required build for patch DG*5.3*919. NOTE: Master Patient Index (MPI) enhancements are being distributed in three VistA namespaces: DG, RG and MPIF. The enhancements related to this patch are only being distributed in the DG and MPIF VistA namespaces. MPIF*1.0*62 should be installed before DG*5.3*919 for non-legacy sites (do NOT install MPIF*1.0*62 on legacy sites), as the new Swipe/Scan process being exported in this patch will not work without MPIF*1.0*62. Therefore it is recommended that these patches be installed in the following order on non-legacy sites: MPIF*1.0*62 and then DG*5.3*919. DG*5.3*919 should be installed immediately after installing MPIF*1.0*62. NOTE: Legacy sites can install just the DG*5.3*919 patch, as legacy sites won't use the data capture process. MPIF*1.0*62 should NOT be installed on legacy sites. Enhancement The enhancement exported in this patch updates the routine DPTLK so that anytime a Veteran Health Information Card (VHIC) or the Department of Defense's (DoD) Common Access Card (CAC) is presented and swiped or scanned at the facility, the activity is captured and stored locally at the site in the ^XTMP("MPIFCARD") global location. This stored activity data which consists of the card's ID, type of Card (VHIC or CAC) and the event type (swipe or scan) will be downloaded nightly by the Master Patient Index (MPI) for use by the Healthcare Identity Management (HC IdM) team for reporting purposes. Issue WorldVistA#1 Routines DPTLK4 and DPTLK7 were updated so that the WHO ENTERED PATIENT field (#.096) in the PATIENT file (WorldVistA#2) is populated for new patients registered with the REGISTER A PATIENT [DG REGISTER PATIENT] menu option. Issue WorldVistA#2 Finally, routines DPTLK4 and DPTLK7 were also updated to ensure that the 'NEW PATIENT ADDED TO SYSTEM' MailMan messages are generated when a new patient is registered at the Veterans Affairs Medical Center (VAMC) through the REGISTER A PATIENT [DG REGISTER PATIENT] menu option. Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A CA Ticket(s) & Overview --------------------------- 1. I7264886FY16 - WHO ENTERED PATIENT field (#.096) in the PATIENT file (WorldVistA#2) no longer populated Problem: -------- After the release of patch DG*5.3*915 it was determined that the WHO ENTERED PATIENT field (#.096) of the PATIENT file (WorldVistA#2) was not being populated after a new patient was registered with the REGISTER A PATIENT [DG REGISTER PATIENT] menu option. After further investigation, this issue was found to be a long standing problem, but only when a patient was registered with either a legacy Veterans Identification Card (VIC) or the newer VHIC cards. This issue went unnoticed until now due to the limited use of these cards. Resolution: ----------- Updates were made to the patient registration software, specifically routines DPTLK4 and DPTLK7, to populate the WHO ENTERED PATIENT field (#.096) in the PATIENT file (WorldVistA#2) when a patient registration is performed with a legacy VIC or newer VHIC cards or through the REGISTER A PATIENT [DG REGISTER PATIENT] menu option. Note: This field is historically populated directly by the REGISTATION (DG) software and not a FileMan (FM) trigger. Test Sites: ---------- C.W. Bill Young (Bay Pines) VAMC Robley Rex (Louisville) VAMC VA Connecticut HCS Patch Installation: Pre/Post Installation Overview ------------------------------ There are no Pre/Post installation routine processes. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/b0ced814/Packages/Registration/Patches/DG_5.3_919

Patch Subject: CPRS GUI v30.B Description: ============ The Computerized Patient Record System (CPRS) Graphical User Interface (GUI) v30.B is an enhancement release with the following modifications: 1) Clinic Orders: Clinic Orders will focus on clinic medications (the ordering, processing and documenting administration of the clinic medication). The enhancements and new functionality to CPRS, Legacy Pharmacy and BCMA will provide the following: a) CPRS - Clinic Medication Orders will function comparable to Inpatient Medications. In addition, CPRS will allow all authorized VHA personnel with prescribing privileges to easily recognize and access a One Step process to document clinic orders and the administration by the clinician from any area where orders can be called. b) BCMA will work with Clinic Medication Orders no matter what the patient status (Inpatient or Outpatient) is ensuring the same BCMA standard of care for medication administration in all clinics. Note: These changes will eliminate the need for outpatients being admitted to a non-count ward/clinic. c) Improved Patient Safety by allowing order checks for 'clinic' orders. d) Improved Patient Safety by implementing the same bar code scanning methodology used in BCMA - to ensure the Five Rights of medication administration is applied to administering clinic order medications. e) Improved Work flows by providing easy access and minimal steps to write a clinic order, process and document administration for clinic medications. 2) Consult Order Dialog Change: A request has been made to rename a field in the Computerized Patient Record System (CPRS) Consult Order Dialog from 'Earliest Appropriate Date' (EAD) to 'Clinically Indicated Date' (CID). This is being done to support new Veterans Access, Control, and Accountability Act (VACAA) guidelines for measuring wait times. Patches GMRC*3.0*81 and GMTS*2.7*112 also contain information regarding this change and are being released in conjunction with OR*3*350. The following changes are being implemented. a) The order and edit/resubmit dialogs for both consult and procedure orders, the SF-513, the Consults tab detail display and the order details view on the Orders tab are all updated to use the CID nomenclature. b) The ORCDGMRC EARLIEST DATE DEFAULT parameter is being replaced by a new parameter, ORCDGMRC CLIN IND DATE DEFAULT. The EAD parameter was restricted to a PACKAGE level value. The CID parameter allows for DIVISION, SYSTEM, and PACKAGE. The PACKAGE level value will be exported as NULL, which will force a provider to actively choose a date when placing consult/procedure orders. c) A new option, ORW CLIN IND DATE DFLT, has been added to the OR PARAM COORDINATOR MENU. This option will allow users to assign DIVISION and/or SYSTEM level values to the ORCDGMRC CLIN IND DATE DEFAULT parameter. 3) Lab Display Status: Targets changes to lab and report tab display changes. 4) Software changes are being made to correct several Patient Safety Issues (PSPOs), and additional miscellaneous defect fixes. For a complete listing of patches included in this release, please refer to the CPRS GUI v.30.b (Patch OR*3.0*350) Release notes. Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- DISPLAY GROUP (#101.41) Modified OE/RR REPORT (#101.24) Modified OE/RR NOTIFICATIONS PROCESSING FLAGS New (#100.9) (#2) ORDER DIALOG (#101.41) Modified Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- OR BCMA ORDER COM Broker Modified OR CPRS GUI CHART Broker Modified OR DEBUG REPORT Action New OR PARAM IRM MENU Menu Modified OR PARAM COORDINATOR Menu Modified MENU ORW CLIN IND DATE DFLT Action New Parameters Associated: Parameter Name New/Modified/Deleted -------------- -------------------- OR LAB TAB DEFAULT REPORT New OR REPORT DATE SELECT TYPE New ORCDGMRC CLIN IND DATE New DEFAULT OR MOB DLL VERSION New ORPARAM OVER DATELINE New Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Remote Procedure Calls Associated: Remote Procedure Call Name New/Modified/Deleted -------------------------- -------------------- ORBCMA5 JOB New ORBCMA5 LOCK New ORBCMA5 UNLOCK New ORDEBUG SAVEDESC New ORDEBUG SAVERPCS New ORQQCN GET USER AUTH Modified ORUTL ISCLORD New ORUTL4 DLL New ORWDXM1 BLDQRSP Modified ORWRP1A RADIO New ORWU OVERDL New ORQQPL EDIT LOAD Modified ORWPS COVER Modified ORWU MOBAPP New Security Keys Associated: Security Key Name ----------------- ORSUPPLY Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: Developer Issues ----------------- 1. Non-VA Medication Quick Order Dialogs with Complex Dosages Problem ------- It is possible to create non-VA medication quick orders with complex dosages even though the Document Herbal/OTC/Non-VA Medications dialog in the Computerized Patient Record System Graphical User Interface (CPRS GUI) does not handle complex quick orders. Resolution ---------- The ability to create non-VA medication quick order dialogs with complex dosages is now removed. During the post-install, a report will be generated listing all non-VA medication quick order dialogs with complex dosages. Sites may edit these order dialogs to remove the complex dosages at their discretion. 2. Post CPRS v29 Report Issues Problem ------- Two issues were identified with the printing of reports released with Computerized Patient Record System (CPRS) version 29: a. When printing any of the electronic Prescribing for Controlled Substances (ePCS) reports installed with patch OR*3*218 to a printer, blank pages are randomly inserted in the reports. The quick order reports released with patch OR*3*366 also exhibit this problem. b. Sites find it difficult to identify the users on the Provider Incomplete Configuration Report who need immediate assistance versus those who do not (for example, differentiating between physicians and nurse practitioner). Resolution ---------- The issues are corrected as follows: a. All of the reports are corrected to no longer insert blank pages. b. Providers' title will now appear on the Provider Incomplete Configuration Report to assist sites in determining which users they need to take action on. 3. CPRS v27 Inpatient Medication Order Detailed Display Issue Problem ------- CPRS version 27 introduced a problem with the Order Details dialog box when viewing a complex inpatient medication order. The dialog box did not show the order's schedule. Resolution ---------- The code is modified to properly display the order's schedule for complex inpatient medication orders. New Service Requests (NSRs) ---------------------------- 20070506 - Clinic Orders (Partially) Clinic Orders will focus on clinic medications (the ordering and processing of the clinic medication). In the Orders tab of CPRS, there are two new medication dialog options: Clinic Medications and Clinic Infusion. Clinic Medication Orders will function comparable to Inpatient Medications. In addition, the new functionality provides a warning to indicate to the user that a past date was chosen when ordering a clinic medication for future administration. Patient Safety Issues (PSIs) ----------------------------- PSI-03-043/PSPO 44/PSPO 1495 Outpatient medication orders entered with DONE as a priority did not appear on the Meds tab in CPRS, were never sent to Outpatient Pharmacy and were missed in future order checks. See Remedy ticket 67690 for resolution. PSI-05-083/PSPO 218 Item #4 Inpatient Medication orders only appear on the Orders tab and not on the Meds tab or in BCMA. These orders will now display in all areas. Also, a priority of DONE could be selected when using the Inpatient Medication order dialog in CPRS GUI. See Remedy ticket 108406 for resolution. PSI-06-038/PSPO 299 When an outpatient with non-VA medications is admitted, the non-VA medications appear on the inpatient's coversheet in the Active Medications section and appear in the Active Orders view on the Orders tab. See associated Remedy tickets HD136027 and HD180136 for resolution. PSI-07-027/PSPO 480 When the hold is removed from an order in CPRS, the status the order had when it was placed on hold is the same status that displays when the user attempts to sign the order. If the order is expired, this status is not updated and displayed to the user unless the user refreshes the screen. This is true for other actions such as pending to active. See associated Remedy ticket HD176676 for resolution. PSPO 1187 Tubefeeding orders are confusing and not communicating issues to providers. So, they are difficult to get correct. See Remedy ticket 290535 for resolution. PSPO 1201 When a provider processes an unsigned order alert, occasionally a blank Orders tab is presented, which may lead the provider to believe that no action is necessary. This happens because the unsigned order has lapsed by the time the alert is processed. See associated Remedy ticket HD293275. PSPO 1267 When a provider orders a medication for an outpatient using the inpatient medication order dialog, the order appears on the Orders tab in the Outpatient Medications display group and on the Medications tab in the Inpatient section. See associated Remedy ticket HD280989 for resolution. PSPO 1604 Users can create CPRS personal quick orders with a value for the Schedule field and a blank Dose field. When creating system-wide quick orders in VistA, the Schedule field cannot be filled unless a value is placed in the Dose field. This happens because the VistA Quick Order editor does not allow entry into a child item if the parent item is blank. See associated Remedy ticket HD366596 for resolution. PSPO 1913 and 2149 The user is able to create multiple sessions with patient context for each session when there should only be one CPRS with patient context. See associated Remedy tickets 449620 and 580169 for resolution. PSPO 1664 A speech pathologist noticed during inpatient rounds that a delayed order of "soft + thins" diet was activated upon patient transfer. However, this patch was at risk of dyspepsia. See Remedy ticket 385397 for resolution. PSPO 2052 When a patient requests a renewal for a non-renewable Schedule II controlled substance through the AudioCARE AudioRenewal module, an informational alert is generated that contains the drug name in the message. When processed, the alert simply disappears. See associated Remedy tickets HD478854 and HD717451 for resolution. PSPO 2165 A problem was reported with notes not being saved under the following conditions: 1) Boilerplated note title used to enter a progress note, 2) User used the right/left mouse buttons simultaneously with the middle wheel to zoom on the text. However when attempting to recreate this problem in CPRS GUIv29 the notes were consistently saved. See associated Remedy ticket 354377 for resolution. PSPO 2221 A provider was entering an inpatient medication order when CPRS had an abnormal termination. See Remedy 614497 for resolution. PSPO 2334 When a user processes a lab notification and proceeds to switch patients, the notification message text of the previous notification does not clear out in the header caption of the labs tab. See associated Remedy ticket INC000000768368 for resolution. Defect Tracking System Ticket(s) & Overview: -------------------------------------------- HD136027 HD180136 HD176676 HD215437 HD238394 HD335195 HD390473 HD293275 HD366596 HD514882 HD478854 HD717451 HD481460 HD280989 INC000000067690 INC000000069154 INC000000069312 INC000000070157 INC000000070588 INC000000108406 INC000000172679 INC000000202393 INC000000290535 INC000000343735 INC000000423142 INC000000470004 INC000000882041 INC000000892823 INC000000901156 INC000000910219 INC000001202824 INC000000614497 INC000000385397 INC000000449620 INC000000580169 INC000000358459 INC000000418697 INC000000237478 INC000000276632 INC000000388190 INC000000449476 INC000000532291 INC000000583696 INC000000337933 INC000000274701 INC000000279302 INC000000469465 INC000000070106 INC000000217354 INC000000354377 INC000000481233 INC000000181466 INC000000174830 INC000000069384 INC000000070680 INC000001089151 INC000000768368 I6220103FY16 1. HD136027 Non-VA meds show as active order on Inpatients HD180136 Non VA Meds Display Question Problem: ------- Two issues were identified with these tickets: (1) For inpatients, CPRS lists non-VA medications in the Active Orders view on the Orders tab. (2) For inpatients, CPRS lists non-VA medications in the Active Medications section on the Coversheet. Resolution: ---------- Issue 1 is resolved by filtering out non-VA medications from the Active Orders view. The Current Orders view will continue to include non-VA medications. Issue 2 is resolved by filtering out non-VA medications from the Active Medications section on the coversheet for inpatients. 2. HD176676 1 CPRS issue Problem: ------- Two issues were identified with this ticket: (1) When an inpatient medication order with a status of hold expires (its stop date is in the past), the order status is not updated to expired. Any user is then able to release that expired order from hold. This gives the false impression that the order is once again active since the Pharmacy and BCMA packages consider the order expired. (2) When Pharmacy changes a held medication order's status, the order text continues to say HOLD regardless of the new status. Resolution: ---------- Issue 1 is addressed in associated patch PSJ*5*267. OR*3*350 addresses issue 2 by modifying the code that handles HL7 messages from the Pharmacy package. Whenever an order with a status of hold changes status, a release from hold action is always created before changing the order's status. 3. HD215437 2 Med order says HOLD, but has been released from HOLD HD238394 2 Reinstate of D/C of order on provider hold does not remove hold on order tab from order text HD335195 Medication order still has "HOLD" in front of it on Orders Tab but has been released from hold HD390473 2 Med Still on hold on Orders tab, Active on Meds tab Problem: ------- When a pharmacist either holds or releases a hold on a medication order from within the Pharmacy package, the order text on the Orders tab is not synced with the order status (when the status is HOLD, the text does not contain HOLD or when the text contains HOLD, the status is ACTIVE). Resolution: ---------- The code that handles HL7 messages from the Pharmacy package was modified so that regardless of the nature of order selected by the pharmacist, an action will always be created when an order is held and when an order is released from hold. 4. HD280989 Inpatient Med Pkg Order sent to Outpt Med Display Group Problem: ------- When a provider uses the inpatient medications order dialog to order a medication for an outpatient, the resulting order is displayed in the outpatient medications display group on the orders tab and in the inpatient section on the Medications tab. Resolution: ---------- This issue is indirectly fixed by the redesign of clinic medications. When a provider uses the inpatient medication order dialog to order a medication for an outpatient, CPRS will prompt the provider to confirm that they intend to place a clinic medication order. If the provider proceeds, the resulting order will appear in the clinic medications display group on the Orders tab and in the Inpatient Medications section on the Medications tab. 5. HD293275 ALERTS DISAPPEARING ON REFILLS, ORDERS NO LONGER THERE Problem: ------- CPRS lapses orders that remain unsigned after the number of days specified in parameters OR LAPSE ORDERS and OR LAPSE ORDERS DFLT. When the provider processes the unsigned order alert and the order has already lapsed, a blank Orders tab is presented. Resolution: ---------- Patch OR*3*280 (CPRS version 28) added functionality to remove the unsigned order alert when the referenced order is lapsed. OR*3*350 introduces the LAPSED UNSIGNED ORDER notification that when processed, will present the Orders tab to the provider showing which unsigned orders were lapsed. This notification is exported with the following parameter values set at the package level: ORB ARCHIVE PERIOD: 30 days ORB DELETE MECHANISM: Individual Recipient ORB FORWARD SUPERVISOR: 0 (never) ORB FORWARD SURROGATES: 0 (never) ORB PROCESSING FLAG: Disabled ORB PROVIDER RECIPIENTS: OAPT (Ordering provider, Attending provider, Primary provider, and Team) ORB URGENCY: High 6. HD366596 1 Quick Order Does not allow blank DOSAGE HD514882 3 Stack Error when returning through fields of a Quick Order Problem: ------- When creating system-wide quick orders in VistA, the Schedule field cannot be filled unless a value is placed in the Dose field. This happens because the VistA Quick Order editor does not allow entry into a child item if the parent item is blank. Resolution: ---------- Users can now create both simple and complex system-wide quick orders with a blank dosage field. 7. HD478854 Audio Renewal request HD717451 AudioRenewal alerts for controlled substance Rx missing Problem: ------- Renewal requests for non-renewable Schedule II controlled substances generate an informational alert that when processed, is simply deleted. This may cause the provider to accidentally miss placing the renewal order. Resolution: ---------- The existing OP RX RENEWAL REQUEST notification is converted into an action alert that when processed, will take the user to the Orders tab which shows only the non-renewable order. This alert has also been renamed to OP NON-RENEWABLE RX RENEWAL to reflect the change in the notification's functionality. 8. HD481460 6 SCHEDULE required for quick orders Problem: ------- Users cannot create system quick orders with a blank value for the Schedule field. In addition, users cannot delete a value from the And/Then conjunction field for complex dosing quick orders. Resolution: ---------- The Schedule field is no longer a required field and users are now able to leave the And/Then conjunction field blank. 9. INC000000882041 OERR - Other: Duplicate VA numbers INC000000892823 <UNDEFINED>DUPVAQ+16~ORDEA01A *DISINC Problem: ------- When the Duplicate VA Numbers report is queued, the error <UNDEFINED>DUPVAQ+16~ORDEA01A *DISINC is generated and the report does not generate. Resolution: ---------- The code that queues the report is modified to properly save the DISINC variable. 10. INC000000614497 Inpatient medication and CPRS order locked issue Problem: ------- A provider was entering an inpatient medication order when CPRS had an abnormal termination. This set a patient lock for the record and the provider was not able to enter additional orders. Resolution: ---------- Multiple potential lock issues were identified and have been addressed. The lock and unlock code now falls inside of a Try/Finally statement which will force the unlock to fire when the code terminates. 11. INC000000385397 Correct activation of a delayed diet order caused a patient to be fed an inappropriate diet Problem: ------- It was noticed by a speech pathologist during inpatient rounds at the reporting site that a delayed order of "soft + thins" diet (this is a thin watery diet) was activated upon patient transfer as expected, however since the patient was at risk of dyspepsia (difficulty in swallowing), they should have remained on the "nectar thick" diet (this is a thicker liquid diet with a consistency of honey) they were on prior to transfer. Resolution: ---------- Modifications were made to the current software (pop-up) so that users are prompted with both current and future delayed orders when entering new diet orders. 12. INC000000449620 More than one session of CPRS with patient context INC000000580169 CCOW ISSUE WHEN ONE SESSION IS EDITING AN ORDER Problem: ------- The user was able to create multiple sessions with patient context for each session when there should only be one CPRS with patient context. There were multiple instances where a modal window would prevent the CPRS application from accepting messages. This would prevent the session from closing the window and switching to the proper context. Resolution: ---------- The code was modified to check if order sets, order dialogs or order action windows were modal, if so then we would allow CPRS to close the window and process the context request. 13. INC000000358459 "Edit Common List" rearrange issue Problem: ------- When using "Edit Common List" as you would move the position a selected item, a tool tip would appear and halt all other events until an item in the list was clicked. This usually happened around the third click. Resolution: ---------- This has to do with the ItemTipEnabled property. To combat this issue the OnClick events for the up and down buttons were moved into the OnMouseDown event. When the MouseDown event fires the ItemTipEnabled is set to false and then returned to on when the MouseUp event is fired. 14. INC000000418697 Use of Recall appointments for writing orders Problem: ------- When writing an order for a recall appointment a user with the ORES key would correctly be prompted about the missing date/time. However if the user had either the ORELSE key or the OREMAS key they would not receive the prompt and later when the order was saved would receive an M Error. Resolution: ---------- To correct this issue an additional check was put in for the change and copy actions. This check will verify that a location exist and time has been selected. If not the user will see the correct prompt. 15. INC000000237478 Error saving notes Document #: 0 Problem: ------- When completing/updating a consult the user tries to write a second note via the notes tab. The second note is completed and signed and the user tries to return to the original consult note. When attempting to save the consult note they receive the save error. Resolution: ---------- This issue is caused because CPRS is only designed to handle one note Edit at a time. Code has been added that will inform the user of this fact just as it does on the notes tab. 16. INC000000276632 Provider comments in outpatient medications Problem: ------- A provider was trying to change the preexisting comments for an outpatient medication and did not uncheck the patient instruction box. The user must remember to uncheck the patient instruction box or the providers previous comments show up in the current script along with the new comments. Resolution: ---------- The patient instruction label has been modified to now read "Patient Instructions - A check in this box below WILL INCLUDE the patient instructions in this order." A hint was added to the patient instruction check box that states "A check in this box WILL INCLUDE the patient instructions in this order." 17. INC000000388190 Sorting issue on consult service list Problem: ------- When ordering a consult, the consult to service list does not sort properly Resolution: ---------- There was a custom sort method that did not function as expected. This has now been rewritten to correctly sort by a specific piece. 18. INC000000449476 Pharmacy Objects do not print correctly Problem: ------- This is an addition to remedy ticket INC000000144336 (released in CPRS 28). It was found at test sites that a carriage return was not being added if the print space was less than 10 characters. Resolution: ---------- Modified method to now include a carriage return when length is less than 10 characters. 19. INC000000070157 Prevent duplicate entry of IV components Problem: ------- Currently, the CPRS IV (Infusion) ordering dialog allows for the selection of the same item multiple times. Resolution: ---------- The dialog was modified to prevent selection of the same additive multiple times. 20. INC000000337933 Quick Order creation: missing additional dose box Problem: ------- When creating quick orders via the GUI there was no way to save the order with the "Give additional dose now" check box checked. Resolution: ---------- When the quick order is saved via the GUI the check box will have its state saved. 21. INC000000274701 Review/Sign Changes doesn't display previous session unsigned orders Problem: ------- CPRS is designed to hold both the current session changes and the previous sessions changes in the same variable. When either selecting a new patient or refreshing the current patient, CPRS returns all changes and loads them to a global variable. If the select new patient is cancelled and the review/sign changes action is used again, the variable is overwritten with the changes from prior sessions. Resolution: ---------- A temporary list is made that will be used to restore the change list in case the user cancels out of the patient selection. 22. INC000000279302 Duration or Total Volume list doesn't enforce unique selection Problem: ------- When placing an infusion order the Duration of Total Volume list box does not enforce unique entries before auto selecting. The selection box contains both Days and Doses and when a provider types in "D" it will select the first "D" word in the list. In this case Days would be auto selected. Resolution: ---------- To correct this the auto complete functionality needed to be rewritten to now take in unique matches before selecting from the list. 23. INC000000469465 Attempting to add a new interdisciplinary note Problem: ------- When viewing the notes while they are sorted by title the user was trying to add an interdisciplinary note to an actual note (right pane of notes tab) and not the interdisciplinary group (left pane of notes tab). Resolution: ---------- The condition that was used to determine if the actions should show was not fired when the selecting an item from the note pane (right). The logic has been moved into its own method so that it can be called from both panes as needed. 24. INC000000070106 Restricting OI for Lab Orders Problem: ------- When an orderable item (lab) is set as "QuickOrder restricted" it is being restricted from both Labs and quick-order. Resolution: ---------- An update was made to the orderable items RPC to now check if the dialog is a quick order or not. Using this information the return list can now filter appropriately. 25. INC000000217354 Reminder dialog templates allow ordering of consult tracker services Problem: ------- When a service is set up as a tracking only service a user without the proper rights is able to make a quick order as a finding item. This is inconsistent with the way that it works directly through consults. Resolution: ---------- When making a consult quick order, check if the service is set to grouping. If so, then stop and display the error. If it is marked as tracking then check if the user has the correct rights (user level) and if so, then continue, else halt and display message. 26. INC000000354377 Increased margins due to zooming in on the note Problem: ------- When using the zoom feature while editing a note, the margins increase width causing the text to wrap at one character per line. The background auto save of the note fires off and saves the note in this format. Resolution: ---------- The zoom functionality was removed from CPRS since it was not intended to be used. 27. INC000000481233 Change button loses position Problem: ------- Change button loses position with dual monitors. If you expand your display greater than the width of your main display, the change button will overwrite information. Resolution: ---------- To ensure that the button does not lose its position the anchor properties for the button need to be modified. The code that was used to try to calculate the position is not needed since these anchors can do this for us. 28. INC000000181466 Automatically defaulting cosigner name Problem: ------- When entering a note the cosigner name is carried over from previous notes. Resolution: ---------- There was code that was once designed to set the cosigner to the last one used. Since there is now an option to specify the default cosigner, this code is irrelevant. 29. INC000000174830 Long delay with no hourglass for "all signed notes" view Problem: ------- When loading a large number of notes for a patient there is no "hourglass" letting the user know that CPRS is still working. Resolution: ---------- The issue dealt with building the tree list of the notes. CPRS would take some time to build this list and not show an hourglass to the user. An hourglass has been added to this loop as well as rewriting the loop to get a 94% speed increase. 30. INC000000069384 Sign on chart for transcriptionist Problem: ------- A transcriptionist writes a note and tries to sign it, they are presented with the "sign on chart" option. However when doing this the document remains in an unsigned status. Resolution: ---------- This option is designed for orders and the logic that determines if this option should show needed to be corrected. 31. INC000000070680 Orders - Active time period honored by Auto D/C Release Event Problem: ------- On the orders tab if the custom view is changed to "only list placed During time period" then only active orders for that time period are displayed. However, if "auto d/c release events" view is then used only the ones that fall in the time period used from the prior view are displayed. Resolution: ---------- The dates used to filter the results should be cleared when using the "AutoDC/Release Event Orders" view. 32. INC000001089151 Health Summary - Health Summary Component: Problem: ------- The medication reconciliation tool (part of Health Summary) does not include non-VA medications for inpatients. This was the result of code changes for patient safety issue PSI-06-038/PSPO 299 to remove non-VA medications from the Active Medications section on the cover sheet for inpatients. Resolution: ---------- The code was further modified to return non-VA medications when called by the medication reconciliation tool only; the coversheet will continue to filter out non-VA medications for inpatients. 33. INC000000768368 Lab Results Problem: ------- When a provider processes a lab results notification for a particular patient and then proceeds to switch patient records, the notification message text of the previous patient's lab results was still displayed under the header caption of the Most Recent Labs view on the Labs tab. This may cause the provider to misinterpret the lab results for the current patient. Resolution: ---------- The software has been corrected so that after lab notification processing and switching of patients, the previous lab notification text will be cleared out from the header caption display of the current patient's lab results. 34. INC000000067690 WPB-0803-30791 done ordrs not appearing on meds tab INC000000069154 INC000000343735 Problem: ------- Outpatient medication orders entered in CPRS using the Priority of DONE do not appear on the meds tab. This is because they are considered to be already completed. Resolution: ---------- DONE is being removed as a priority. Providers are being encouraged to use the new feature for One-Step Clinic Admin orders that will ensure orders are in Pharmacy as well as CPRS. 35. INC000000069312 ORDER DIALOG 'PSO SUPPLY' INC000000423142 Problem: ------- The PSO SUPPLY dialog has never worked correctly. It still required a user to be authorized to write medication orders. Solution: -------- Changes have been made to the supply order dialog to allow a user with the OR SUPPLY key to write supply orders without being authorized to write medication orders. 36. INC000000070588 RX showing complete status. Can select DONE as a INC000000108406 priority Problem: ------- This is a long-outstanding patient safety issue. The final requirement to fully correct the item was to create the One-Step Clinic Admin functionality for providers. Solution: -------- Created the One-Step Clinic Admin functionality for providers. 37. INC000000172679 Problem with IMO order Problem: ------- The root problem is with the fact that IMO was never intended to handle an Inpatient. Solution: -------- Clinic Orders (the replacement for IMO) will handle clinic orders for Inpatient as well as Outpatients. This is done in conjunction with the changes already released in Inpatient Medications. 38. INC000000202393 Flagging an unreleased Inpatient Med order doesn't appear in Pharmacy Problem: ------- Flagging an unreleased Inpatient Medications order was causing an issue because the flag information was not appearing in Pharmacy. Solution: -------- The flag is now passed to Pharmacy so they can display it. 39. INC000000290535 Tubefeeding order increased in difficulty Problem: ------- Tubefeeding orders are confusing. Solution: -------- Hover text was added, calculations were corrected to prevent entering something with over the maximum amount of fluids and the help text was updated to remove the unapproved abbreviations. 40. INC000000470004 Choosing note titles to display within OPTIONS Problem: ------- On the Notes tab within Options you can configure a document list preference. But, when you try to choose a title from the Document Class of Discharge Summary and then "Save Changes", it doesn't work the way it does when you set note titles at the Progress Note Document Class. When you go into create a New Summary, the title you chose within the options does not appear at the top of my list of discharge summary notes. Solution: -------- Corrected display of discharge summary notes. 41. INC000000532291 Complex quick orders with empty dose rows load as simple orders. Problem: ------- If a complex quick order with an empty dose row loads into the GUI it loads as a simple order. Solution: -------- The call that loads the quick orders has been modified to correctly deal with empty dose rows. 42. INC000000583696 Each succeeding diet order makes box shrink Problem: ------- For each subsequent diet order placed, the order dialog box continues to shrink. When entering a diet order on an inpatient, the Diet Order box appears fairly normal, e.g., they can see the entire order box (Accept Order/Quit). But then with each subsequent order the box shrinks. Solution: -------- Sizing of box has been modified to remain consistent. 43. INC000000901156 Drug name appended to dose for Complex Order Problem: ------- The problem with trailing spaces had been corrected previously for simple orders. However, complex orders had not been addressed. The issue being that trailing spaces on drug names were causing the drug name to be appended incorrectly. Solution: -------- Drug names with trailing spaces no longer cause the drug name to be appended incorrectly to the dosage text. 44. INC000000910219 Inpatient Medications: Other INC000001202824 Receiving 'invalid integer' error when renewing Problem: ------- When renewing Inpatient Medications orders, there could be an issue with receiving an 'invalid integer' error. Solution: -------- When renewing an order an error could occur that would prevent that action from happening in the CPRS GUI. This has been corrected to ensure that when the referencing the number of days it uses a default of 0 instead of experiencing an invalid integer error. 45. I6220103FY16 Diagnoses are being removed from the Encounter if NOT initially added to the Problem List Problem: ------- When editing a completed note encounter and adding the previous primary diagnosis to the Problem List, the newly added SNOMED/ICD-10 primary diagnosis is not saved in CPRS & PCE and the previous ICD-10 diagnosis is removed from the encounter. This resulted in errors and potentially lost workload/VERA if the encounters are not corrected. This applies only to diagnoses that are NOT initially added to the Problem List and that are added later. Solution: -------- This is corrected so that the newly added diagnoses are saved appropriately in CPRS and PCE when editing a completed note encounter. Test Sites: =========== Cleveland, OH Heartland - East Heartland - West Loma Linda, CA Palo Alto, CA San Diego, CA Software and Documentation Retrieval Instructions: -------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. Sites may retrieve the software and/or documentation directly using the Secure File Transfer Protocol (SFTP) address as directed by the CPRS Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Order+Entry+Results+Reporting/Patches/OR_3.0_350

Patch Subject: TELEPATHOLOGY MAINTENANCE Description: ============ Associated Patches: This patch must be installed after MAG*3.0*162. Subject: TELEPATHOLOGY UPDATE Category: OTHER Description: =========== MAG*3.0*173 has emergency fixes for the VistA Imaging processing Laboratory (LAB) images of Telepathology. It will fix email notifications being generated because of an error and some undefined error issues when the LAB images are processed in the Text Gateway. Patch Components: ================ This patch includes software and documentation files. This document, MAG3_0P 173_Patch_Description.pdf, provides an overview, explains the changes, and outlines the installation for this patch. MAG3_0P173_README.txt, if present, is an informative file associated with the patch. Software: File Name Description MAG3_0P173.KID Kernel Installation and Distribution System (KIDS) build for Patch Documentation: ============= This document, MAG3_0173_Patch_Description.pdf, provides an overview, explains the changes, and outlines the installation for this patch. Files & Fields Associated: ========================= There are no files or fields associated with this patch. Forms Associated: ================ There are no forms associated with this patch. Mail Groups Associated: ====================== There are no mail groups associated with this patch. Options Associated: ================== There are no options associated with this patch. Protocols Associated: ==================== There are no protocols associated with this patch. Security Keys Associated: ======================== There are no security keys associated with this patch. Templates Associated: ==================== There are no templates associated with this patch. Additional Information: ====================== New Service Requests (NSRs): =========================== There are no new service requests addressed in this patch. Patient Safety Issues (PSIs): ============================ There are no patient safety issues associated with this patch. Defect Tracking System Ticket(s) & Overview: 1. Defect 194669 (Tickets I9738934FY16, I10130099FY16, and ========================================================== I10236113FY16) Anatomic Pathology Generating HL7 Email Alerts ============================================================= Problem: Multiple sites have reported receiving an email notification of an HL7 Anatomic pathology issue. The notification is: An error occurred in EDIT^MAGT7MA when trying to create and/or send an HL7 message. The error message is as follows: "-53`No test found in LAB(60) file for LRSS="SP"" Please notify your local IRM Staff. Several issues were identified: 1. The variables LRI and LRDFN are sometimes not being passed in the HL7 message from the Laboratory system to Telepathology. 2. The Internal Entry Number (IEN) numbers for LAB codes CY (Cytology), EM (Electron Microscopy) and SP (Surgical Pathology) were hardcoded, but it was found that they can be different at each site. Resolution: The following modifications were made: 1. If the LRI or Data File Number (DFN) are null in the HL7 message, the study is ignored. 2. Instead of hardcoding the IEN associated with a lab code, the routine was modified to look up the IEN of the procedure by searching the LABORATORY TEST file #60 by the lab procedure. 2. Defect 194632 (Tickets R9978605FY16 and I10155657FY16) Text Gateway ======================================================================= Error "PATIENT NOT IN DATABASE" ============================== Problem: Sites are reporting that the Text Gateway was generating the error "PATIENT NOT IN DATABASE" in the PID segment of HL7 messages which delayed or halted Text Gateway processing. This error occurred because the LAB referral patient was not registered in the VistA Patient database. Some patients are defined within the laboratory package itself, but not in the VistA Patient file. For example, patients that are referrals are in the REFERRAL PATIENT files (#67) but may not be in the VISTA PATIENT file (#2). Resolution: The new VistA MAGT7MA routine resolves this issue by checking the PARENT FILE field (#.02) of the LAB DATA file (#63). If the PARENT FILE field is not "PATIENT", the order is skipped. Test Sites: ========== The following sites are test sites for this patch: Milwaukee Minneapolis Iron Mountain Phoenix Software and Documentation Retrieval Instructions: ================================================= Software being released and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from [email protected] from the COMMAND prompt (example: sftp [email protected]). This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: When using Attachmate Reflection (Secure Shell): Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext When using the COMMAND prompt (example: sftp [email protected]): Albany: [email protected] Hines: [email protected] Salt Lake City: [email protected] Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/. Patch Installation: ================== Pre/Post Installation Overview: ============================== MAG*3.0*173 must be installed on the VistA System. This patch must be installed by the compliance date to conform to VHA Directive 2001-023. All sites running VistA Imaging 3.0 must install the KIDS portion of this patch. This patch can be loaded while the VistA Imaging System is active and users are on the system. Installing the MAG*3.0*173 KIDS only takes 2-3 minutes. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Imaging/Patches/MAG_3.0_173

Patch Subject: REMOVE LIST MANAGER RESTRICTIONS ON MNEMONICS Description: ============ The OR*3.0*422 patch allows the use of special characters (particularly punctuation) within the Order Menu Management Menu Editor. A previous VistA patch disallowed use of special characters. The patch was intended to prevent display problems within ListManager; however, most sites are using the Computerized Patient Record System (CPRS) Graphical User Interface (GUI) and the inability to utilize punctuation can negatively impact the clarity of menu options and instructions. This modification restores the ability to use certain special characters in Order Menu Management so that users can more clearly specify order menu options. Use of the following special characters will now be allowed: hyphen (-), comma (,), and equal sign (=). Use of the caret (^) and semicolon (;) are still restricted because they are used as field delimiters in VistA. Additional changes will be made to the Data Dictionary elements of the ORDER DIALOG (#101.41) file to modify the Help displayed when entering a question mark at a VistA prompt. The affected fields are: * ORDER DIALOG (#101.41) file, DISPLAY TEXT (#2) field * ORDER DIALOG (#101.41) file, ITEMS (#10) sub-file, DISPLAY TEXT (#4) field This intake has been implemented locally at the VA centers in Fargo, ND; Sioux Falls, SD; Meade, MD; Minneapolis, MN; Omaha, NE; Richmond, VA; St. Cloud, MN; Seattle, WA; Milwaukee, WI; Hot Springs, AR; Des Moines, IA; and Iowa City, IA. The NSR for this intake addresses the following requirement: * VHBAO: NEED3045 Provide the ability for the users to include punctuation and other special characters in CPRS order menu notes. Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted --------------------- -------------------- -------------------- ORDER DIALOG (#101.41) DISPLAY TEXT (#2) MODIFIED ORDER DIALOG, ITEMS (#101.412) DISPLAY TEXT (#4) MODIFIED Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: New Service Requests (NSRs) ---------------------------- NSR 20131108 REMOVE LISTMANAGER RESTRICTIONS ON MNEMONICS Patient Safety Issues (PSIs) ----------------------------- N/A Remedy Ticket(s) & Overview --------------------------- N/A Problem: -------- N/A Resolution: ----------- N/A Test Sites: Hunter Holmes McGuire VA Medical Center (Richmond) Orlando VA Medical Center William S. Middleton Memorial Veterans Hospital (Madison) VA Central Plains Health Care System (Omaha, Lincoln, Grand Island of NE, Des Moines, Knoxville, Iowa City of IA) Software and Documentation Retrieval Instructions: ---------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ Title File Name FTP Mode ----------------------------------------------------------------------- CPRS RELEASE NOTES: GUI VERSION OR_3_0_422_RN.PDF binary Pre/Post Installation Overview ------------------------------ Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Order+Entry+Results+Reporting/Patches/OR_3.0_422

Patch Subject: MASTER VETERAN INDEX VISTA ENHANCEMENTS - ITERATION 16 RELEASE 2 Description: ============ ************************************************************************* * This patch may be installed with users on the system, however we * * strongly advise it be installed after business hours. * ************************************************************************* NOTE: To prevent legacy systems ending up as Treating Facilities, RG* and MPIF* patches should NOT be installed on legacy systems. MPIF*1.0*60, DG*5.3*926 and FB*3.5*173 are the required builds for patch MPIF*1.0*64. NOTE: Master Patient Index (MPI) enhancements are being distributed in four VistA namespaces: DG, MPIF, RG and FB. The only build enforced requirements are that: - FB*3.5*173 and DG*5.3*926 be installed prior to MPIF*1.0*64 - DG*5.3*926 be installed prior to RG*1.0*65 Therefore non-legacy sites can install FB*3.5*173 and DG*5.3*926 in any order, then install MPIF*1.0*64 and RG*1.0*65 patches in any order (Do NOT install MPIF*1.0*64 or RG*1.0*65 on legacy sites). NOTE: Legacy sites can install just the DG*5.3*926 and FB*3.5*173 patches. MPIF*1.0*64 and RG*1.0*65 should NOT be installed on legacy sites. Enhancement This enhancement patch provides additional support to allow the Master Veteran Index (MVI) to support the Date of Death of patients at the medical facilities. Enhancement WorldVistA#1 A new remote procedure (RPC) [MPIF DOD ACTIVITY CHECK] was created to search through various packages: FEE BASIS, OUTPATIENT PHARMACY, PCE PATIENT CARE ENCOUNTER, REGISTRAION and SCHEDULING, to find any activity that might indicate that a patient is not actually deceased. The validity of the reported Date of Death will be confirmed if no activity is found. Routine MPIFDODC was created to support the functionality in this RPC. Enhancement WorldVistA#2 Routine MPIFA31B was updated to build and retrieve the parsed OBX A31 Health Level Seven (HL7) Patient update message segments for the following additional Date of Death fields in the PATIENT (WorldVistA#2) file: - DATE OF DEATH LAST UPDATED (#.354) - SUPPORTING DOCUMENT TYPE (#.357) - DATE OF DEATH OPTION USED (#.358) Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------------- -------------------- MPIF DOD ACTIVITY CHECK NEW Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A Remedy Ticket(s) & Overview --------------------------- N/A Test Sites: ---------- Central Alabama HCS Indianapolis VAMC Louisville VAMC Software and Documentation Retrieval Instructions: ---------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext PIMS ADT Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/application.asp?appid=55 Title File Name FTP Mode --------------------------------------------------------------------------- PIMS ADT User Manual - Bed Control Menu DG_5_3_P926_BC_UM.PDF (binary) PIMS ADT User Manual - Registration Menu DG_5_3_P926_REG_UM.PDF (binary) MPI/PD VistA Documentation can also be found on the VA Software Documentation Library at: http://www.domain.ext/vdl/application.asp?appid=16 Title File Name FTP Mode --------------------------------------------------------------------------- MPI/PD VISTA User Manual RG_1_0_P65_UM.PDF (binary) MPI/PD VISTA Programmer Manual RG_1_0_P65_PM.PDF (binary) MPI/PD VISTA Technical Manual RG_1_0_P65_TM.PDF (binary) Patch Installation: Pre/Post Installation Overview ------------------------------ There are no Pre/Post installation routine processes. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/6

Patch Subject: TREASURY CROSS-SERVICING PROGRAM Description: ============ ***************************************************************************** This patch supports changes to the Veterans Health Information System and Technology Architecture (VistA) for the Treasury Cross-Servicing Program (TCSP). PRCA*4.5*301 (Accounts Receivable-AR) is being released in host file: PRCA_45_P301.KID. It is imperative that these patches be installed no later than the compliance date. Your understanding and support is appreciated. ***************************************************************************** The Chief Business Office (CBO) requested modifications to the VistA Accounts Receivable Package to support the next phase in the implementation of the Debt Collection Improvement Act (DCIA) of 1996 by the Department of Veterans Affairs (VA). This patch modifies the Account Receivable (AR) v4.5 application as described below: 1. TOP Modifications - Exclude first party bills from the TOP process unless the date the bill became active is prior to the Activation Date. Do not exclude bills from the TOP process that are identified as referred to TOP. 2. DMC Referral Flag - The VistA system shall not modify the 90-day DMC debt referral process. 3. Referral File - The VistA system shall automatically create a file of delinquent first party bills. - The VistA system shall create the file in IAI format, containing record types H, 1, 2, 2A, 2C, 3, Z. - The VistA system shall schedule the batch process to create the referral file once per week for new referrals. - The VistA system shall have the ability to stop a bill from being referred to Cross-Servicing. 4. Update File - The VistA shall create a batch task to generate a file of updated information for previously referred bills. - The VistA system shall create the file in IAI format, containing record types H, 1, 2, 2A, Z. - The VistA system shall schedule the batch process to create the update file once per week for new referrals. - The VistA system shall have the ability to stop a bill from being updated to Cross-Servicing. 5. Recall File - The VistA shall create a batch task to generate a file to recall previously referred bills by debt, debtor, or case. - The VistA system shall create the file in IAI format, containing record types H, 1, 2, 3, Z. - The VistA system shall schedule the batch process to create the recall file once per week for new referrals. - The VistA system shall have the ability to stop a bill from being recalled to Cross-Servicing. 6. Reconciliation File - The VistA shall create a batch task to generate a file of updated information for Reconciliation bills. 7. Monthly Patient Statements - Bills Referred to Cross-Servicing - The VistA system shall exclude the value of bills that have been referred to Cross-Servicing from the 'Previous Balance' and 'Balance' block on the monthly patient statement. 8. Monthly Patient Statements - Bills Not Referred to Cross-Servicing - The VistA system shall include the value of bills in the 'Previous Balance' and 'Balance' block on the monthly patient statement when a bill is no longer referred to Cross-Servicing. 9. Unprocessable File - Bills that are sent for referral to Cross- Servicing but are deemed not valid are rejected and returned to VistA with the source of the error and the error code. The rejected debts and error codes are stored historically and reported in debts profile reports and reject reports. 10. Due Process Notification (DPN) - A letter notification system for debts expected to be sent to Cross-Servicing. From Cross-Servicing initialization, debts under $25.00 will be tracked for one year. As the debts become qualified to Cross-Servicing referral, AITC will be notified to send due process letters. After a sixty day waiting, if the debts become qualified, the debts will be referred to Cross- Servicing in the usual fashion. 11. Cross-Servicing Qualified / No Third Letter Sent - A bulletin will be generated by VistA when there is eligible debt for Cross- Servicing and a third collection letter has not been sent. The bulletin will contain the debtor's name and bill number(s). 12. Activation Date - The VistA system shall not refer bills to Cross-Servicing if they were not active prior to the Activation Date. For Little Rock #598, Beckley #517, and Upstate NY #528 the Activation Date has been set to February 1, 2015. For all other sites, the Activation Date has been set to August 1, 2015. Patch Components: ================= Files & Fields Associated: -------------------------- The following is a list of files included in this patch: File Name (Number) Field Name (Number) New/Mod/Del ------------------ ------------------- ----------- AR DEBTOR (#340) TCSP RECALL FLAG field (#7.02) NEW TCSP RECALL DATE field (#7.03) NEW TCSP RECALL REASON field (#7.04) NEW DATE DEBTOR REFERRED TO TCSP field(#7.05 NEW AR DEBTOR (#342) CROSS-SERVICING START DATE field (#100) NEW AR BATCH PAYMENT (#344) RECEIPT PAY TYPE field (#.19) NEW AR BATCH PAYMENT (#344) Subfile TRANSACTION (#344.01) PATIENT NAME OR BILL NUMBER (#.09) MOD LOCKBOX TRANSACTION CODE (#.15) NEW TCS IAI ERROR CODES (#348.5) ERROR CODE ID (#.01) NEW FIELD NAME/ACTION (WorldVistA#1) NEW RECORD TYPE (WorldVistA#2) NEW ERROR MESSAGE (#3) NEW TCS IAI ACTION CODES (#348.6) ACTION CODE (#.01) NEW ACTION DESCRIPTION (WorldVistA#1) NEW RECORD TYPE (WorldVistA#2) NEW TCS IAI RECORD TYPES (#348.7) RECORD TYPE ID (#.01) NEW RECORD TYPE DESCRIPTION (WorldVistA#1) NEW DATA TYPE (WorldVistA#2) NEW ACCOUNTS RECEIVABLE (#430) DATE BILL REFERRED TO TCSP field (#151) NEW TCSP RECALL FLAG field (#152) NEW TCSP RECALL EFF. DATE field (#153) NEW TCSP RECALL REASON field (#154) NEW RECALL AMOUNT field (#155) NEW STOP TCSP REFERRAL FLAG field (#157) NEW STOP TCSP REFERRAL EFF. DATE field (#158) NEW STOP TCSP REFERRAL REASON field (#159) NEW STOP TCSP REFERRAL COMMENT field (#159.1) NEW TCSP CASE RECALL FLAG field (#159.2) NEW TCSP CASE RECALL EFF DATE (#159.3) NEW TCSP CASE RECALL REASON (#159.4) NEW TCSP GENDER (#159.5) NEW ORIGINAL TCSP TIN field (#161) NEW ORIGINAL TCSP DEBTOR NAME field (#162) NEW TCSP DELINQUENCY DATE field (#163) NEW TCSP DEBTOR ADDRESS, LINE 1 field (#164) NEW TCSP DEBTOR ADDRESS, LINE 2 field (#165) NEW TCSP DEBTOR ADDRESS, CITY field (#166) NEW TCSP DEBTOR ADDRESS, STATE field (#167) NEW TCSP DEBTOR ZIP CODE field (#168) NEW ORIGINAL TCSP AMOUNT field (#169) NEW CURRENT TCSP AMOUNT field (#169.1) NEW TCSP DEBTOR PHONE (#169.2) NEW TCSP COUNTRY CODE (#169.3) NEW TCSP DOB (#169.4) NEW DUE PROCESS NOTIFICATION FLAG (#173) NEW DUE PROCESS REQUEST DATE (#174) NEW DUE PROCESS LETTER PRINT DATE (#175) NEW DUE PROCESS REFERRAL DATE (#176) NEW DUE PROCESS ERROR DATE (#177) NEW DUE PROCESS ERROR CODES (#178) NEW SEND TCSP RECORD 1 field (#191) NEW SEND TCSP RECORD 2 field (#192) NEW SEND TCSP RECORD 2A field (#193) NEW SEND TCSP RECORD 2C field (#194) NEW STOP INTEREST ADMIN CALC (#199.2) NEW RETURNED DATE (#301) NEW RETURN REASON CODE (#302) NEW COMPROMISED INDICATOR (#303) NEW COMPROMISE AMOUNT (#304) NEW CLOSED DATE (#305) NEW BANKRUPTCY DATE (#306) NEW DATE OF DEATH (#307) NEW DATE OF DISSOLUTION (#308) NEW ACCOUNTS RECEIVABLE (#430) Subfile CS DECREASE ADJ TRANS NUMBER (#430.0171) CS DECREASE ADJ TRANS NUMBER (#.01) NEW SEND TCSP RECORD 5B NEW ACCOUNTS RECEIVABLE (#430) Subfile REJECT DATE (#430.0172) REJECT DATE (#.01) NEW REJECT SOURCE (WorldVistA#1) NEW REJECT REASON1 (WorldVistA#2) NEW REJECT REASON2 (#3) NEW REJECT REASON3 (#4) NEW REJECT REASON4 (#5) NEW REJECT REASON5 (#6) NEW REJECT REASON6 (#7) NEW REJECT REASON7 (#8) NEW REJECT REASON8 (#9) NEW REJECT REASON9 (#10) NEW RECORD TYPE (#11) NEW RECORD ACTION CODE (#12) NEW REJECT BATCH ID (#13) NEW REJECT MM MSG NO. (#14) NEW AR RETURN REASON CODE (#430.5) CODE (#.01) NEW DESCRIPTION (WorldVistA#1) NEW CATEGORY (WorldVistA#2) NEW Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- TCSP NEW TPC NEW TPL NEW Options Associated: Option Name Type New/Modified/Deleted ----------- ----------- ------------------------ PRCAF SUPERVISOR MENU MENU MODIFIED RCTCSP BILL REPORT RUN ROUTINE NEW RCTCSP IAI ERROR CODES LIST RUN ROUTINE NEW RCTCSP MENU MENU NEW RCTCSP RECALL REPORT RUN ROUTINE NEW RCTCSP RECALLB RUN ROUTINE NEW RCTCSP RECALLD RUN ROUTINE NEW RCTCSP RECONCIL REPORT RUN ROUTINE NEW RCTCSP REJ SERVER SERVER NEW RCTCSP REJECT REPORT RUN ROUTINE NEW RCTCSP REPORT RUN ROUTINE NEW RCTCSP STOP RUN ROUTINE NEW RCTCSPD SERVER SERVER NEW RCTCSPR SERVER SERVER NEW Protocols Associated: --------------------- N/A Security Keys Associated: ------------------------- Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Mod/Del ------------- ---- ------------------ ----------- PRCA MEANS PROFILE PRINT ACCOUNTS RECEIVABLE MOD (#430) PRCA OTHER PROFILE PRINT ACCOUNTS RECEIVABLE MOD (#430) PRCA PROFILE PRINT ACCOUNTS RECEIVABLE MOD (#430) PRCA TCSP RECALLB PRINT ACCOUNTS RECEIVABLE NEW (#430) PRCA TCSP RECALLD PRINT ACCOUNTS RECEIVABLE NEW (#430) TCS IAI ERROR CODES LIST PRINT TCS IAI ERROR CODES NEW (#348.5) Remote Procedure New/Mod/Del ---------------- ----------- N/A Additional Information: N/A New Service Request (NSRs): --------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Remedy Ticket(s) & Overview: ---------------------------- N/A Test Sites: ----------- VISN 16, Region 2, Central Arkansas Veterans Healthcare System, John L. McClellan Memorial Veterans Hospital, Station #598, Little Rock, Arkansas VISN 2, Region 4, VA Health Care Upstate New York, Station #528. VISN 6, Region 3, VA Mid-Atlantic Health Care Network, Beckley VA Medical Center, Station #517, Beckley, West Virginia. VISN 6, Region 3, VA Mid-Atlantic Health Care Network, W. G. (Bill) Hefner VA Medical Center, Station #659, Salisbury, North Carolina. VISN 23, Region 2, Nebraska-Western Iowa Health Care System, Omaha VA Medical Center, Station #636, Omaha, Nebraska. Documentation Retrieval Instructions: ===================================== Updated documentation describing the new functionality introduced by this patch is available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext The documentation will be in the form of Adobe Acrobat files. The following files should be downloaded in the binary SFTP mode. Filename Description -------- ----------- prca_4_5_p301_um.pdf Cross-Servicing User Manual prca_4_5_p301_rn.pdf Cross-Servicing Release Notes / Installation Guide prca_4_5_p301_tm.pdf Accounts Receivable Technical Manual / Security Guide Documentation can also be found on the VA Software Documentation Library at: http://www.domain.ext/vdl/ Patch Installation: =================== Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/6

Patch Subject: FIXED MEDICATION COPAYMENT TIERS (FMCT) Description: ============ This patch will provide enhancements to the National Drug File (NDF) package for Fixed Medication Copayment Tiers (FMCT) project. It supports the redesign and/or enhancement of the current structure of charges for first-party outpatient medication copayments to treat non-service connected conditions. This project brings the Department of Veterans Affairs (VA) into compliance with the Proposed Rule 38 Code of Federal Regulations (CFR) Part 17 Copayments for Medications. This patch is the first in a series of patches and provides the infrastructure for copayment tiers to add data dictionary modifications to support subsequent FMCT patch releases. This specific patch contains the following functionality: --------------------------------------------------------- 1. The REDUCED COPAY multiple field (#45) is deleted from VA PRODUCT file (#50.68). This multiple is not used and has never been populated. A post install routine (PSNP476E) is included in this patch to perform this deletion and the post install routine will be deleted during patch install. 2. The new COPAY TIER multiple field (#45) in VA PRODUCT file (#50.68) is added and will be populated with tier level information. Patch Components: ---------------- Files & Fields Associated: -------------------------- File Name (Number) Field Name (Number) New/Modified/Delete ------------------ -------------------------- ------------------- VA PRODUCT file (#50.68) REDUCED COPAY multiple(#45) Deleted START DATE (#.01) Deleted STOP DATE (#.02) Deleted VA PRODUCT file (#50.68) COPAY TIER multiple (#45) New COPAY TIER LEVEL (#.01) New COPAY EFFECTIVE DATE (#1) New COPAY END DATE (#2) New Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: ----------------------- N/A New Service Requests (NSRs) --------------------------- Tiered Modification Copayment Structure (#20150208) Patient Safety Issues (PSIs) ---------------------------- N/A Defect Tracking System Ticket(s) & Overview ------------------------------------------- N/A Test Sites: ----------- AMARILLO, TX MARYLAND HCS SHREVEPORT, LA Documentation Retrieval Instructions: ------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ Title File Name FTP Mode ------------------------------------------------------------------------ N/A Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/National+Drug+File/Patches/PSN_4.0_476

Patch Subject: DATA UPDATES - FY17 #2 Description: ============ NOTE: This patch is part of NDF Data Update FY17 #2, which is comprised of three patches, PSN*4*500, PSN*4*505, and PSN*4*501 (to be installed in THIS ORDER) ************************************************************************* This patch inadvertently deletes UNITS data for a list of drugs as outlined in the DATA UPDATE FOR NDF message sent when installing this patch. This will cause issues with matching, possible dosage, and "TRANSMIT TO CMOP" values for these drugs. In order to correct these issues patch PSN*4.0*505 should be installed immediately after this patch, before attempting to rematch these drugs. ************************************************************************* This patch provides updates to data in several of the files associated with the National Drug File (NDF) application. This patch generates four mail messages. All are sent from NDF MANAGER to members of the NDF DATA mail group, holders of the PSNMGR security key, and the person installing the patch. The first message, with the subject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists), dispense units, and associated NDCs, products for which the national formulary indicator has changed, products that have been unmatched from CMOP, products for which the national formulary restriction has changed, and products for which the copay tier has changed. The second, with the subject UPDATED INTERACTIONS, lists interactions that have been added, edited, or inactivated. The third, with the subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the DRUG file (#50) which have been unmatched from NDF. The fourth, with the subject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies which have been changed because they were created with ingredients that are no longer primary ingredients. **ATTENTION: CMOP SITES ONLY** Do not load and install or queue to install this patch while Consolidated Mail Outpatient Pharmacy (CMOP) prescriptions are being transmitted. If transmissions are in progress, incorrect prescription information may be sent to the CMOP. To determine if a CMOP transmission is in progress, examine TaskMan for jobs entitled "CMOP Data Transmission". Associated Remedy Tickets: ========================= I11416996FY17 Test Sites: =========== CENTRAL PLAINS HCS CHILLICOTHE VAMC OKLAHOMA CITY VAMC Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/National+Drug+File/Patches/PSN_4.0_500

Patch Subject: DATA UPDATES - FY17 #2 (UNITS CORRECTION) Description: ============ NOTE: This patch is part of NDF Data Update FY17 #2, which is comprised of three patches, PSN*4*500, PSN*4*505, and PSN*4*501 (to be installed in THIS ORDER) ************************************************************************* This patch updates UNITS data for a list of drugs outlined in the DATA UPDATE FOR NDF message sent when installing this patch. Some units were inadvertently removed with patch PSN*4.0*500 causing issues with matching, possible dosage, and "TRANSMIT TO CMOP" values for these drugs. This patch (PSN*4.0*505) should be installed immediately after patch PSN*4.0*500 to correct these issues before attempting to rematch these drugs ************************************************************************* This patch provides updates to data in several of the files associated with the National Drug File (NDF) application. This patch generates four mail messages. All are sent from NDF MANAGER to members of the NDF DATA mail group, holders of the PSNMGR security key, and the person installing the patch. The first message, with the subject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists), dispense units, and associated NDCs, products for which the national formulary indicator has changed, products that have been unmatched from CMOP, products for which the national formulary restriction has changed, and products for which the copay tier has changed. The second, with the subject UPDATED INTERACTIONS, lists interactions that have been added, edited, or inactivated. The third, with the subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the DRUG file (#50) which have been unmatched from NDF. The fourth, with the subject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies which have been changed because they were created with ingredients that are no longer primary ingredients. **ATTENTION: CMOP SITES ONLY** Do not load and install or queue to install this patch while Consolidated Mail Outpatient Pharmacy (CMOP) prescriptions are being transmitted. If transmissions are in progress, incorrect prescription information may be sent to the CMOP. To determine if a CMOP transmission is in progress, examine TaskMan for jobs entitled "CMOP Data Transmission". Associated Remedy Tickets: ========================= I11514206FY17 Test Sites: =========== CENTRAL PLAINS HCS CHILLICOTHE VAMC OKLAHOMA CITY VAMC Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/National+Drug+File/Patches/PSN_4.0_505

Patch Subject: PMI MAPPING - FY17 #2 Description: ============ NOTE: This patch is part of NDF Data Update FY17 #2, which is comprised of three patches, PSN*4*500, PSN*4*505, and PSN*4*501 (to be installed in THIS ORDER) The environment check routine for this patch checks to see that the installer is a valid user. The post-install routine for this patch matches entries in the VA PRODUCT file (#50.68) to the proper PMIs. Associated Remedy Tickets: ========================== I11416996FY17 Test Sites: =========== CENTRAL PLAINS HCS CHILLICOTHE VAMC OKLAHOMA CITY VAMC Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/National+Drug+File/Patches/PSN_4.0_501

Patch Subject: MASTER VETERAN INDEX VISTA ENHANCEMENTS - ITERATION 16 RELEASE 2 Description: ============ ************************************************************************* * This patch may be installed with users on the system, however because * * the patient lookup routines are being exported with this patch, we * * strongly advise that it be installed after business hours. * ************************************************************************* DG*5.3*901, DG*5.3*902, DG*5.3*915 and DG*5.3*919 are the required builds for patch DG*5.3*926. NOTE: Master Patient Index (MPI) enhancements are being distributed in four VistA namespaces: DG, MPIF, RG and FB. The only build enforced requirements are that: - FB*3.5*173 and DG*5.3*926 be installed prior to MPIF*1.0*64 - DG*5.3*926 be installed prior to RG*1.0*65 Therefore non-legacy sites can install FB*3.5*173 and DG*5.3*926 in any order, then install MPIF*1.0*64 and RG*1.0*65 patches in any order (Do NOT install MPIF*1.0*64 or RG*1.0*65 on legacy sites). NOTE: Legacy sites can install just the DG*5.3*926 and FB*3.5*173 patches. MPIF*1.0*64 and RG*1.0*65 should NOT be installed on legacy sites. Enhancements The following enhancements exported in this patch will allow the Master Veteran Index (MVI) to support the Date of Death of patients at the medical facilities. Enhancement #1 The following Data Dictionary changes have been made to support the patient's Date of Death process. - Added a new SUPPORTING DOCUMENTATION TYPES (#47.75) file, that will identify the available documents detailing how a patient's death was recorded. NOTE: File will be exported with data. - Added a new SOURCE OF NOTIFICATIONS (#47.76) file, that will identify the sources for who first notified the Veteran Affairs (VA) of a patient's death. NOTE: File will be exported with data. - Modified the SOURCE OF NOTIFICATION (#.353) field in the PATIENT (#2) file from a SET OF CODES to POINTER to the SOURCE OF NOTIFICATIONS (#47.76) file. NOTE: This modification was done as the additional notifications being added in this patch exceeded the size limit of the SET OF CODES. NOTE: The old code and the new internal entry number (IEN) in the new file are the same, so no additional data modifications to existing patient records in the PATIENT (#2) file is required. - Added the new field SUPPORTING DOCUMENT TYPE (#.357) to the PATIENT (#2) file which points to the SUPPORTING DOCUMENTATION TYPES (#47.75) file. Auditing has been enabled. - Added a FIELD INDEX type cross-reference (X-REF) on the following field: Field Number Field Name X-Ref ------------------------------------------------------- .357 SUPPORTING DOCUMENT TYPE AVAFC357 This new cross-references makes use of the DG FIELD MONITOR tool that was released in patch DG*5.3*527. This tool utilizes the VAFC MPIPD FIELD TRIGGER protocol, which creates an entry in the ADT/HL7 PIVOT (#391.71) file, as well as sets the VAFCF variable to capture the fields that have been modified during an edit. This field will be included in the Health Level Seven (HL7) 2.4 messages generated by the MPI/PD applications. Routine VAFCTR supports this effort. - Added the new field DATE OF DEATH OPTION USED (#.358) to the PATIENT (#2) file which is a SET OF CODES identifying the option used when modifying a patient's Date of Death at the Medical Facility. Auditing has been enabled. - Added the new field PROCESS MVI DOD UPDATE? (#1401) to the MAS PARAMETERS (#43) file, which will determine whether the site should process Date of Death messages from the MVI. Enhancement #2 Routine DGDEATH was updated to prompt the user for the SUPPORTING DOCUMENT TYPE (field #.357 in the PATIENT (#2) file) and the DATE OF DEATH OPTION USED (field #.358 in the PATIENT (#2) file) when the date of death is entered. The previous field values will also be deleted from the PATIENT (#2) file when the date of death is deleted. Note: The restriction of deleting the Date of Death when the death entry is NOT from the local site has now been removed, thus allowing the Date of Death to now be deleted regardless of where the death data entry occurred. In addition, SOURCE OF NOTIFICATION (field #353 in the PATIENT (#2) file) has been restricted to only allow selection of VAMC INPATIENT DEATH or SPOUSE/NEXT OF KIN/OTHER PERSON for deceased patients. Finally, if the death is related to a patient movement, then this information will automatically be populated. Enhancement #3 A new remote procedure (RPC) [VAFC DOD ACCEPT SET/DISPLAY] was created to allow the MVI to toggle the PROCESS MVI DOD UPDATE? (#1401) field in the MAS PARAMETERS (#43) file on and off, which will determine if the site should process Date of Death messages from the MVI. Routine VAFCDODA was created to support the functionality in this RPC. In addition, an Application Program Interface (API) entry point (CHK^VAFCDODA) was created in this routine to allow a quick check of the current setting of this field during execution of updates. NOTE: This RPC is a fail-safe in case issues arise processing Date of Death messages at the site. It will allow MVI to immediately turn Date of Death processing off until the issue(s) have been resolved, instead of requiring the site back out the patches. Enhancement #4 Routine VAFCPDAT was updated to include all of the Date of Death data if they are populated when the PATIENT MPI/PD DATA INQUIRY menu option is executed. Date of Death fields in the PATIENT (#2) file to display include: - DATE OF DEATH (#.351) - DEATH ENTERED BY (#.352) - SOURCE OF NOTIFICATION (#.353) - DATE OF DEATH LAST UPDATED (#.354) - LAST EDITED BY (#.355) - SUPPORTING DOCUMENT TYPE (#.357) - DATE OF DEATH OPTION USED (#.358) Enhancement #5 Routines VAFCQRY and VAFCSB were updated to parse and build the OBX Health Level Seven (HL7) message segments for Date of Death data in the A08, A31 and A19 HL7 messages. Issue #1 Routine DPTLK7 was updated to move the pseudo Social Security Number (SSN) reason prompt directly under the SSN prompt, so that if a user enters a pseudo SSN they are immediately prompted for a reason, which will now be a required response. This will eliminate the non-required pseudo reason prompt that was displayed later on in the process. Issue #2 Finally, routine DGREG was updated to restore the Insurance Data retrieval call in the REGISTER A PATIENT [DG REGISTER PATIENT] menu option, which was inadvertently left out of Enterprise Registration. Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- MAS PARAMETERS (#43) PROCESS MVI DOD NEW UPDATE? (#1401) PATIENT (#2) SOURCE OF MODIFIED NOTIFICATION (#.353) SUPPORTING DOCUMENT NEW TYPE (#.357) DATE OF DEATH OPTION NEW USED (#.358) SOURCE OF NOTIFICATIONS (#47.76) NEW File (Data Exported) SUPPORTING DOCUMENT TYPES (#47.75) NEW File (Data Exported) Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------------- -------------------- VAFC DOD ACCEPT SET/DISPLAY NEW Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A CA Ticket(s) & Overview --------------------------- 1. I10555752FY16/I8707336FY16 - Patient Treatment File (PTF) issue caused by Pseudo SSN. Problem: -------- Sites have reported issues when registering patients with a pseudo SSN, detailing that their messages are being rejected by Austin. This is due to the fact that pseudo SSN reason is not always being populated for patients with pseudo SSNs. Pseudo SSN reason is required for Austin when the patient has a pseudo SSN, but is not a required field in the PATIENT file (#2). In addition, the pseudo SSN reason is also not required to be populated for a patient who is assigned a pseudo SSN in the REGISTER A PATIENT ([DG REGISTER PATIENT] menu option) process for Enterprise Registration. However, it is required when adding a patient through the LOAD/EDIT PATIENT DATA [DG LOAD PATIENT DATA] menu option. Resolution: ----------- Routine DPTLK7 was updated so that pseudo SSN reason will now be a required prompt in the Enterprise Registration process when the patient is assigned a pseudo SSN. Note: The pseudo SSN reason prompt will be moved so it is directly underneath the SSN prompt. The user will only be prompted for this reason if they assign a pseudo SSN to the patient and a response will now be required to continue the registration process. The non-required pseudo SSN reason prompt that was previously displayed later on in the registration process will be removed. 2. I9418203FY16 - Insurance inconsistency questions during the Registration process. Problem: -------- Sites have reported that when using the REGISTER A PATIENT [DG REGISTER PATIENT] menu option that the Insurance data retrieval was removed when the Register Once functionality was replaced with Enterprise Registration. Resolution: ----------- Routine DGREG was updated to restore the inadvertently removed Insurance data retrieval call from the REGISTER A PATIENT [DG REGISTER PATIENT] menu option for Enterprise Registration. Test Sites: ---------- Central Alabama HCS Indianapolis VAMC Louisville VAMC Software and Documentation Retrieval Instructions: ---------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext PIMS ADT Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/application.asp?appid=55 Title File Name FTP Mode --------------------------------------------------------------------------- PIMS ADT User Manual - Bed Control Menu DG_5_3_P926_BC_UM.PDF (binary) PIMS ADT User Manual - Registration Menu DG_5_3_P926_REG_UM.PDF (binary) MPI/PD VistA Documentation can also be found on the VA Software Documentation Library at: http://www.domain.ext/vdl/application.asp?appid=16 Title File Name FTP Mode --------------------------------------------------------------------------- MPI/PD VISTA User Manual RG_1_0_P65_UM.PDF (binary) MPI/PD VISTA Programmer Manual RG_1_0_P65_PM.PDF (binary) MPI/PD VISTA Technical Manual RG_1_0_P65_TM.PDF (binary) Patch Installation: Pre/Post Installation Overview ------------------------------ There are no Pre/Post installation routine processes. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Registration/Patches/DG_5.3_926

Patch Subject: MCCF EINSURANCE FY15 549 WARRANTY Description: ============ *** Note: This patch has a mandatory 3 day installation compliance. The purpose of this patch is to meet the requirements of the Medical Care Collection Fund (MCCF) eInsurance Compliance Phase 3 project related to Integrated Billing (IB). eInsurance provides Insurance identification and verification which is vital to the success of the Department of Veterans Affairs (VA) revenue collection process. Accurate insurance information is needed to effectively submit claims and collect payments from third-party payers for medical care and services provided to Veterans by the Veterans Health Administration (VHA). The following feature of the IB software will be affected by this project: The VistA software has been updated to re-evaluate the patient's current insurance coverage when they are identified in VistA as being deceased. Note, that if the date of death entered is TODAY or NOW or TODAY-1 then the 'COVERED BY HEALTH INSURANCE' field (#2,.3192) will remain at "Y" if they have an active policy on file, as the automated process associated with the 'DATE OF DEATH' field (#2,.351) would term that policy with the date of death+1. A term date of TODAY or NOW or TODAY+1 is considered an active policy when it is evaluated. Patch Components ================ Files & Fields Associated: File Name (#) New/Modified/ Sub-file Name (#) Field Name (Number) Deleted ------------------- --------------------------------- ------------- N/A Bulletins Associated: New/Modified/ Bulletin Name Deleted ------------- ------------- N/A Dialogs Associated: New/Modified/ Dialog Name Deleted ----------- ------------- N/A Forms Associated: New/Modified/ Form Name File Name (Number) Deleted --------- ------------------ ------------- N/A Functions Associated: New/Modified/ Function Name Deleted ------------- ------------- N/A HL Logical Link: New/Modified/ HL Logical Name Deleted --------------- ------------- N/A HL7 Application Parameters: New/Modified/ HL7 Parameter Name Deleted ------------------ ------------- N/A HLO Application Registry: New/Modified/ HLO Registry Name Deleted ----------------- ------------- N/A Help Frames Associated: New/Modified/ Help Frame Name Deleted --------------- ------------- N/A Mail Groups Associated: New/Modified/ Mail Group Name Deleted --------------- ------------- N/A Options Associated: New/Modified/ Option Name Type Deleted ----------- ---- ------------- N/A Parameter Definitions: New/Modified/ Parameter Name Deleted -------------- ------------- N/A Parameter Template: New/Modified/ Template Name Deleted ------------- ------------- N/A Protocols Associated: New/Modified/ Protocol Name Deleted ------------- ------------- N/A Remote Procedures Associated: New/Modified/ Remote Procedure Name Deleted --------------------- ------------- N/A Security Keys Associated: New/Modified/ Security Key Name Deleted ----------------- ------------- N/A Templates, Input Associated: New/Modified/ Template Name Type File Name (Number) Deleted ------------- ---- ------------------ ------------- N/A Templates, List Associated: New/Modified/ Template Name Type Deleted ------------- ---- ------------- N/A Templates, Print Associated: New/Modified/ Template Name Type File Name (Number) Deleted ------------- ---- ------------------ ------------- N/A Templates, Sort Associated: New/Modified/ Template Name Type File Name (Number) Deleted ------------- ---- ------------------ ------------- N/A Additional Information: ---------------------- N/A New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A Remedy Ticket(s) & Overview --------------------------- 1. Ticket #R11229286FY17 Inconsistent Data Elements report Problem: ------- As a result of automated processes in IB*2.0*549, when a patient is identified as deceased in VistA the patient's active policies are termed. However, the field 'COVERED BY HEALTH INSURANCE' (#2,.3192) is not updated to accurately reflect the proper status of the patient's insurance coverage. Resolution: ---------- The VistA software has been updated to re-evaluate the patient's current insurance coverage when they are identified in VistA as being deceased. Note, that if the date of death entered is TODAY or NOW or TODAY-1 then the 'COVERED BY HEALTH INSURANCE' field (#2,.3192) will remain at "Y" if they have an active policy on file, as the automated process associated with the 'DATE OF DEATH' field (#2,.351) would term that policy with the date of death+1. A term date of TODAY or NOW or TODAY+1 is considered an active policy when it is evaluated. Patient Safety Issues (PSIs) --------------------------------- N/A Defect Tracking System Ticket(s) & Overview --------------------------------------------------------- N/A Test Sites: ------------- VA Nebraska Western Iowa Health Care System Chillicothe VA Medical Center Documentation Retrieval Instructions --------------------------------------------- Updated documentation describing the new functionality introduced by this patch is available. The preferred method is to SFTP the files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve software directly from a specific server. Sites may retrieve the documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany domain.ext Hines domain.ext Salt Lake City domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ Title File Name FTP Mode ------ --------- -------- Release Notes/Installation Guide ib_2_0_p579_rn.pdf Binary Patch Installation: Pre/Post Installation Overview ------------------------------------- The installation of this patch may be QUEUED. To avoid disruptions, this patch should be installed during non-peak hours when there is minimal activity on the system and there are no Integrated Billing users on the system. Do not delete the post install routine "IBY579PO" after the install has been completed, as a task has been queued to run in the background and it needs this routine to complete. ******************************************************************** * You may want to rebuild the 'INCONSISTENT DATA' file (#38.5) * * 24 hours after IB*2.0*579 is installed. One may run/queue the * * option that is described below in the post installation * * instructions. * ******************************************************************** Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Integrated+Billing/Patches/IB_2.0_579

Patch Subject: 2017 MEANS TEST THRESHOLDS Description: ============ ************************************************************************** * Per VHA FACT SHEET titled MEANS TEST AND GEOGRAPHIC-BASED MEANS TEST * * AND MAXIMUM ANNUAL RATES OF PENSION FOR CALENDAR YEAR 2017, this * * patch MUST be installed AS SOON AS POSSIBLE. The patch is being * * released as an Emergency patch together with EAS*1.0*144 (2017 GMT * * Thresholds) and IB*2.0*583 (2017 RX Copay Thresholds) and may be * * installed out of sequence with respect to other released Registration * * (DG) patches. * ************************************************************************** The Means Test thresholds for Calendar Year 2017 are distributed with this patch. The post-installation routine, DG53930P, will create a new subentry (or replace an existing one) for calendar year 2017 in the MEANS TEST DATA (#250) multiple field of the MAS PARAMETERS (#43) file. This patch, DG*5.3*930, is one of three VistA 2017 threshold patches. It updates the thresholds for the Means Tests and the Maximum Annual Pension Rate. Patch EAS*1.0*144 will address the annual updates for the GMT Thresholds and patch IB*2.0*583 will address the annual updates for the Pharmacy Copay Thresholds. Associated NSR(s): ================== N/A Associated Ticket: ================== R10750194FY16 - 2017 MEANS TEST THRESHOLDS Participating Test Sites: ========================= Altoona - James E. Van Zandt VAMC Wilmingon VAMC VISN 2 - Upstate New York HCS Ticket Overview: ================ R10750194FY16 - 2017 MEANS TEST THRESHOLDS Problem: -------- Annual updates of Means Test thresholds are needed for calendar year 2017 (income year 2016). Resolution: ----------- The post-installation routine, DG53930P, will create a new subentry (or replace an existing one) for calendar year 2017 in the MEANS TEST DATA (#250) multiple field of the MAS PARAMETERS (#43) file. Six subfields within the multiple will be updated with the new Means Test threshold data values as follows: MEANS TEST DATA (#.01) - 2017 MT COPAY EXEMPT VET INCOME (#2) - $32,074 MT COPAY EXEMPT 1ST DEP INCOME (#3) - $6,415 MT COPAY EXEMPT INCOME PER DEP (#4) - $2,205 THRESHOLD PROPERTY (#8) - $80,000 CHILD INCOME EXCLUSION (#17) - $10,400 In addition, this patch will update the following entries in the PARAMETERS file (#8989.5) for Income Year 2016 to: DGMT MAPR GLOBAL RATE 5 DGMT MAPR 0 DEPENDENTS 12907 DGMT MAPR 1 DEPENDENTS 16902 DGMT MAPR N DEPENDENTS 2205 Software Retrieval: =================== The software for this patch is not being distributed through the National Patch Module. This patch is being distributed as a host file. The host file will contain the following three KIDS builds: Host file name: DG_53_930.KID Builds: DG*5.3*930 EAS*1.0*144 IB*2.0*583 Sites may retrieve the software directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany : domain.ext Hines : domain.ext Salt Lake City : domain.ext First Available Server : download.vista.domain.ext The following file will be available: File Name Description --------- ----------- DG_53_930.KID Host File containing KIDS software distribution Note: Use ASCII mode when transferring the .KID file. Use default answers for KIDS load/install questions. Multi-Build: http://code.osehra.org/VistA.git/blob/master/Packages/MultiBuilds/DG_53_930.KID.json Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Enrollment+Application+System/Patches/EAS_1.0_144 Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Integrated+Billing/Patches/IB_2.0_583

Patch Subject: TREASURY CROSS-SERVICING PROGRAM Description: ============ ***************************************************************************** This patch supports changes to the Veterans Health Information System and Technology Architecture (VistA) for the Treasury Cross-Servicing Program (TCSP). PRCA*4.5*301 (Accounts Receivable-AR) is being released in host file: PRCA_45_P301.KID. It is imperative that these patches be installed no later than the compliance date. Your understanding and support is appreciated. ***************************************************************************** The Chief Business Office (CBO) requested modifications to the VistA Accounts Receivable Package to support the next phase in the implementation of the Debt Collection Improvement Act (DCIA) of 1996 by the Department of Veterans Affairs (VA). This patch modifies the Account Receivable (AR) v4.5 application as described below: 1. TOP Modifications - Exclude first party bills from the TOP process unless the date the bill became active is prior to the Activation Date. Do not exclude bills from the TOP process that are identified as referred to TOP. 2. DMC Referral Flag - The VistA system shall not modify the 90-day DMC debt referral process. 3. Referral File - The VistA system shall automatically create a file of delinquent first party bills. - The VistA system shall create the file in IAI format, containing record types H, 1, 2, 2A, 2C, 3, Z. - The VistA system shall schedule the batch process to create the referral file once per week for new referrals. - The VistA system shall have the ability to stop a bill from being referred to Cross-Servicing. 4. Update File - The VistA shall create a batch task to generate a file of updated information for previously referred bills. - The VistA system shall create the file in IAI format, containing record types H, 1, 2, 2A, Z. - The VistA system shall schedule the batch process to create the update file once per week for new referrals. - The VistA system shall have the ability to stop a bill from being updated to Cross-Servicing. 5. Recall File - The VistA shall create a batch task to generate a file to recall previously referred bills by debt, debtor, or case. - The VistA system shall create the file in IAI format, containing record types H, 1, 2, 3, Z. - The VistA system shall schedule the batch process to create the recall file once per week for new referrals. - The VistA system shall have the ability to stop a bill from being recalled to Cross-Servicing. 6. Reconciliation File - The VistA shall create a batch task to generate a file of updated information for Reconciliation bills. 7. Monthly Patient Statements - Bills Referred to Cross-Servicing - The VistA system shall exclude the value of bills that have been referred to Cross-Servicing from the 'Previous Balance' and 'Balance' block on the monthly patient statement. 8. Monthly Patient Statements - Bills Not Referred to Cross-Servicing - The VistA system shall include the value of bills in the 'Previous Balance' and 'Balance' block on the monthly patient statement when a bill is no longer referred to Cross-Servicing. 9. Unprocessable File - Bills that are sent for referral to Cross- Servicing but are deemed not valid are rejected and returned to VistA with the source of the error and the error code. The rejected debts and error codes are stored historically and reported in debts profile reports and reject reports. 10. Due Process Notification (DPN) - A letter notification system for debts expected to be sent to Cross-Servicing. From Cross-Servicing initialization, debts under $25.00 will be tracked for one year. As the debts become qualified to Cross-Servicing referral, AITC will be notified to send due process letters. After a sixty day waiting, if the debts become qualified, the debts will be referred to Cross- Servicing in the usual fashion. 11. Cross-Servicing Qualified / No Third Letter Sent - A bulletin will be generated by VistA when there is eligible debt for Cross- Servicing and a third collection letter has not been sent. The bulletin will contain the debtor's name and bill number(s). 12. Activation Date - The VistA system shall not refer bills to Cross-Servicing if they were not active prior to the Activation Date. For Little Rock #598, Beckley #517, and Upstate NY #528 the Activation Date has been set to February 1, 2015. For all other sites, the Activation Date has been set to August 1, 2015. Patch Components: ================= Files & Fields Associated: -------------------------- The following is a list of files included in this patch: File Name (Number) Field Name (Number) New/Mod/Del ------------------ ------------------- ----------- AR DEBTOR (#340) TCSP RECALL FLAG field (#7.02) NEW TCSP RECALL DATE field (#7.03) NEW TCSP RECALL REASON field (#7.04) NEW DATE DEBTOR REFERRED TO TCSP field(#7.05 NEW AR DEBTOR (#342) CROSS-SERVICING START DATE field (#100) NEW AR BATCH PAYMENT (#344) RECEIPT PAY TYPE field (#.19) NEW AR BATCH PAYMENT (#344) Subfile TRANSACTION (#344.01) PATIENT NAME OR BILL NUMBER (#.09) MOD LOCKBOX TRANSACTION CODE (#.15) NEW TCS IAI ERROR CODES (#348.5) ERROR CODE ID (#.01) NEW FIELD NAME/ACTION (#1) NEW RECORD TYPE (#2) NEW ERROR MESSAGE (#3) NEW TCS IAI ACTION CODES (#348.6) ACTION CODE (#.01) NEW ACTION DESCRIPTION (#1) NEW RECORD TYPE (#2) NEW TCS IAI RECORD TYPES (#348.7) RECORD TYPE ID (#.01) NEW RECORD TYPE DESCRIPTION (#1) NEW DATA TYPE (#2) NEW ACCOUNTS RECEIVABLE (#430) DATE BILL REFERRED TO TCSP field (#151) NEW TCSP RECALL FLAG field (#152) NEW TCSP RECALL EFF. DATE field (#153) NEW TCSP RECALL REASON field (#154) NEW RECALL AMOUNT field (#155) NEW STOP TCSP REFERRAL FLAG field (#157) NEW STOP TCSP REFERRAL EFF. DATE field (#158) NEW STOP TCSP REFERRAL REASON field (#159) NEW STOP TCSP REFERRAL COMMENT field (#159.1) NEW TCSP CASE RECALL FLAG field (#159.2) NEW TCSP CASE RECALL EFF DATE (#159.3) NEW TCSP CASE RECALL REASON (#159.4) NEW TCSP GENDER (#159.5) NEW ORIGINAL TCSP TIN field (#161) NEW ORIGINAL TCSP DEBTOR NAME field (#162) NEW TCSP DELINQUENCY DATE field (#163) NEW TCSP DEBTOR ADDRESS, LINE 1 field (#164) NEW TCSP DEBTOR ADDRESS, LINE 2 field (#165) NEW TCSP DEBTOR ADDRESS, CITY field (#166) NEW TCSP DEBTOR ADDRESS, STATE field (#167) NEW TCSP DEBTOR ZIP CODE field (#168) NEW ORIGINAL TCSP AMOUNT field (#169) NEW CURRENT TCSP AMOUNT field (#169.1) NEW TCSP DEBTOR PHONE (#169.2) NEW TCSP COUNTRY CODE (#169.3) NEW TCSP DOB (#169.4) NEW DUE PROCESS NOTIFICATION FLAG (#173) NEW DUE PROCESS REQUEST DATE (#174) NEW DUE PROCESS LETTER PRINT DATE (#175) NEW DUE PROCESS REFERRAL DATE (#176) NEW DUE PROCESS ERROR DATE (#177) NEW DUE PROCESS ERROR CODES (#178) NEW SEND TCSP RECORD 1 field (#191) NEW SEND TCSP RECORD 2 field (#192) NEW SEND TCSP RECORD 2A field (#193) NEW SEND TCSP RECORD 2C field (#194) NEW STOP INTEREST ADMIN CALC (#199.2) NEW RETURNED DATE (#301) NEW RETURN REASON CODE (#302) NEW COMPROMISED INDICATOR (#303) NEW COMPROMISE AMOUNT (#304) NEW CLOSED DATE (#305) NEW BANKRUPTCY DATE (#306) NEW DATE OF DEATH (#307) NEW DATE OF DISSOLUTION (#308) NEW ACCOUNTS RECEIVABLE (#430) Subfile CS DECREASE ADJ TRANS NUMBER (#430.0171) CS DECREASE ADJ TRANS NUMBER (#.01) NEW SEND TCSP RECORD 5B NEW ACCOUNTS RECEIVABLE (#430) Subfile REJECT DATE (#430.0172) REJECT DATE (#.01) NEW REJECT SOURCE (#1) NEW REJECT REASON1 (#2) NEW REJECT REASON2 (#3) NEW REJECT REASON3 (#4) NEW REJECT REASON4 (#5) NEW REJECT REASON5 (#6) NEW REJECT REASON6 (#7) NEW REJECT REASON7 (#8) NEW REJECT REASON8 (#9) NEW REJECT REASON9 (#10) NEW RECORD TYPE (#11) NEW RECORD ACTION CODE (#12) NEW REJECT BATCH ID (#13) NEW REJECT MM MSG NO. (#14) NEW AR RETURN REASON CODE (#430.5) CODE (#.01) NEW DESCRIPTION (#1) NEW CATEGORY (#2) NEW Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- TCSP NEW TPC NEW TPL NEW Options Associated: Option Name Type New/Modified/Deleted ----------- ----------- ------------------------ PRCAF SUPERVISOR MENU MENU MODIFIED RCTCSP BILL REPORT RUN ROUTINE NEW RCTCSP IAI ERROR CODES LIST RUN ROUTINE NEW RCTCSP MENU MENU NEW RCTCSP RECALL REPORT RUN ROUTINE NEW RCTCSP RECALLB RUN ROUTINE NEW RCTCSP RECALLD RUN ROUTINE NEW RCTCSP RECONCIL REPORT RUN ROUTINE NEW RCTCSP REJ SERVER SERVER NEW RCTCSP REJECT REPORT RUN ROUTINE NEW RCTCSP REPORT RUN ROUTINE NEW RCTCSP STOP RUN ROUTINE NEW RCTCSPD SERVER SERVER NEW RCTCSPR SERVER SERVER NEW Protocols Associated: --------------------- N/A Security Keys Associated: ------------------------- Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Mod/Del ------------- ---- ------------------ ----------- PRCA MEANS PROFILE PRINT ACCOUNTS RECEIVABLE MOD (#430) PRCA OTHER PROFILE PRINT ACCOUNTS RECEIVABLE MOD (#430) PRCA PROFILE PRINT ACCOUNTS RECEIVABLE MOD (#430) PRCA TCSP RECALLB PRINT ACCOUNTS RECEIVABLE NEW (#430) PRCA TCSP RECALLD PRINT ACCOUNTS RECEIVABLE NEW (#430) TCS IAI ERROR CODES LIST PRINT TCS IAI ERROR CODES NEW (#348.5) Remote Procedure New/Mod/Del ---------------- ----------- N/A Additional Information: N/A New Service Request (NSRs): --------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Remedy Ticket(s) & Overview: ---------------------------- N/A Test Sites: ----------- VISN 16, Region 2, Central Arkansas Veterans Healthcare System, John L. McClellan Memorial Veterans Hospital, Station #598, Little Rock, Arkansas VISN 2, Region 4, VA Health Care Upstate New York, Station #528. VISN 6, Region 3, VA Mid-Atlantic Health Care Network, Beckley VA Medical Center, Station #517, Beckley, West Virginia. VISN 6, Region 3, VA Mid-Atlantic Health Care Network, W. G. (Bill) Hefner VA Medical Center, Station #659, Salisbury, North Carolina. VISN 23, Region 2, Nebraska-Western Iowa Health Care System, Omaha VA Medical Center, Station #636, Omaha, Nebraska. Documentation Retrieval Instructions: ===================================== Updated documentation describing the new functionality introduced by this patch is available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext The documentation will be in the form of Adobe Acrobat files. The following files should be downloaded in the binary SFTP mode. Filename Description -------- ----------- prca_4_5_p301_um.pdf Cross-Servicing User Manual prca_4_5_p301_rn.pdf Cross-Servicing Release Notes / Installation Guide prca_4_5_p301_tm.pdf Accounts Receivable Technical Manual / Security Guide Documentation can also be found on the VA Software Documentation Library at: http://www.domain.ext/vdl/ Patch Installation: =================== Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Accounts+Receivable/Patches/PRCA_4.5_301

Patch Subject: FLOWSHEET TERM UPDATES FROM 04/2014 SPREADSHEET Description: ============ This patch will correct the following issue: 1) The Clinical Procedures (CP) Terminology TERM file (#704.101) and the TERM_TYPE file (#704.102) contain terms used during data entry/display in CP Flowsheet. The Office of Informatics and Analytics - Applied Informatics Services (AIS) Terminology Review Group submitted a spreadsheet requesting additions or updates of 46 Terms. NOTE: These 46 terms were split out over 5 separate tickets for ease of entering, they are not 5 separate issues, but 1 umbrella issue with 1 resolution. ASSOCIATED REMEDY/CA TICKETS: ============================ 1) INC0000000990788 Clinical Procedures - Flowsheets: Terminology Duplicate: I9931080FY16 - Group 1 2) INC0000000991882 Clinical Procedures - Flowsheets: Terminology Duplicate: I9932749FY16 - Group 2 3) INC0000000991895 Clinical Procedures - Flowsheets: Terminology Duplicate: I9933152FY16 - Group 3 4) INC0000001240721 New/modified Terms for CP Flowsheets: Approved CP Terminology Duplicate: I9933514FY16 - Group 4 5) INC0000001244504 Clinical Procedures - Flowsheets: Terminology Duplicate: I9933891FY16 - Group 5 ASSOCIATED NSR(S): ================== N/A PARTICIPATING TEST SITES: ========================= Edward Hines Jr. VA Hospital, IL Huntington VAMC, WV VA Northern California HCS (Mather, Martinez) REMEDY/CA OVERVIEW: =================== 1) INC0000000990788 Clinical Procedures - Flowsheets: Terminology Duplicate: I9931080FY16 - Group 1 Problem 1: ---------- The following list documents the approved changes for Group #1 (Mod) - ADI - SPIRITUAL CARE (Mod) - AIRWAY ARTIFICIAL SIZE - MILIMETERS (Add) - CAUTI Prevention: GU Catheter Discontinued (Mod) - CENTRAL LINE CHANGED (Mod) - CENTRAL LINE DRESSING TYPE (Mod) - CHEST TUBE DRAINAGE CHARACTERISTICS (Mod) - DISCHARGE ACTIVITIES (Add) - DRAIN DRESSING CHANGE 2) INC0000000991882 Clinical Procedures - Flowsheets: Terminology Duplicate: I9932749FY16 - Group 2 Problem 2: ---------- The following list documents the approved changes for Group #2 (Add) - DRAINAGE SYSTEM REPLACED (Add) - DRESSING CHANGE (Mod) - DVT PROPHYLAXIS (Mod) - EDUCATION - BARRIERS (Mod) - EDUCATION - TOPIC (Mod) - ENTERAL NUTRITION TYPE (Add) - EPIDURAL: CATHETER SITE (Mod) - ET LOCATION (Mod) - MUCOUS MEMBRANE CONDITION 3) INC0000000991895 Clinical Procedures - Flowsheets: Terminology Duplicate: I9933152FY16 - Group 3 Problem 3: ---------- The following list documents the approved changes for Group #3 (Add) - NECK EVALUATION (Mod) - BLADDER SCAN - DO NOT CHECK TOTAL OR SUBTOTALS (Mod) - OUTPUT - URINE (Add) - OUTPUT - NASOGASTRIC TUBE (Mod) - PA CATHETER REPOSITIONED/DICONTINUED (Add) - PASERO OPIOID - INDUCED SEDATION SCALE (POSS) (Add) - PREPROCEDURE: DRAINAGE BAG EMPTIED? (Add) - PREPROCEDURE: PLANNED DISPOSITION POST PROCEDURE (Add) - PREPROCEDURE: PULMONARY FUNCTION TEST DONE? (Add) - PREPROCEDURE: SHOWER/BATH W CHLORHEXIDINE SOAP NIGHT BEFORE? 4) INC0000001240721 New/modified Terms for CP Flowsheets: Approved CP Terminology Duplicate: I9933514FY16 - Group 4 Problem 4: ---------- The following list documents the approved changes for Group #4 (Add) - PREPROCEDURE: SHOWER/BATH W CHLORHEXIDINE SOAP THIS AM? (Mod) - PRESSURE ULCER DRAINAGE CHARACTER (Mod) - PULMONARY CARE (Mod) - PULMONARY SECRETION COLOR (Mod) - PULMONARY SUCTIONING SITE (Mod) - PUPIL REACTION (Mod) - PUPIL SIZE (Add) - RESTRAINT CIRCULATION CHECK (Add) - RESTRAINT DEVICE TRIAL RELEASE (Add) - RESTRAINT/SECLUSION DISCONTINUED 5) INC0000001244504 Clinical Procedures - Flowsheets: Terminology Duplicate: I9933891FY16 - Group 5 Problem 5: ---------- The following list documents the approved changes for Group #5 (Mod) - SEDATION SCALE - RAMSEY (Mod) - STOOL COLOR (Add) - TONGUE POSITION (Mod) - IVDOSE RATE - UNITS/HOUR (Mod) - IV FLOW RATE - ml/kg/TIME - DO NOT CHECK TOTAL OR SUBTOTALS (Mod) - LOWER LIMB EXTREMITIES STRENGTH Resolution 1, 2, 3, 4, 5 ------------------------ The above Additions/Updates will be made to the CP Terminology TERM file (#704.101) and the TERM_TYPE file (#704.102). The details of each of these terms is in the Clinical Observation (CliO) Terminology Dictionary And Clinical Data Model Documentation that is listed below. DOCUMENTATION: ============== Documentation is available for the Clinical Observation (CliO) Terminology Dictionary And Clinical Data Model Documentation on the ANONYMOUS.SOFTWARE directory at one of the following Office of Information (OI) Field Offices. Sites will be able to download the documentation in the ".PDF" format. The preferred method is to FTP the files from: Download.vista.domain.ext This transmits files from the first available FTP server. Sites may also elect to retrieve documentation directly from a specific server as follows: Albany ftp.domain.ext Hines ftp.domain.ext Salt Lake City ftp.domain.ext File Name: Description: Protocol: ========== ============ ========= MD1_0P39TERM.PDF CliO Terminology Dictionary Binary And Clinical Data Model Documentation may be found on the System Design and Development Web page at: http://www.domain.ext/vdl Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Clinical+Procedures/Patches/MD_1.0_39

Patch Subject: MASTER VETERAN INDEX VISTA ENHANCEMENTS - ITERATION 16 RELEASE 2 Description: ============ ************************************************************************* * This patch may be installed with users on the system, however we * * strongly advise it be installed after business hours. * ************************************************************************* NOTE: To prevent legacy systems ending up as Treating Facilities, RG* and MPIF* patches should NOT be installed on legacy systems. MPIF*1.0*60, DG*5.3*926 and FB*3.5*173 are the required builds for patch MPIF*1.0*64. NOTE: Master Patient Index (MPI) enhancements are being distributed in four VistA namespaces: DG, MPIF, RG and FB. The only build enforced requirements are that: - FB*3.5*173 and DG*5.3*926 be installed prior to MPIF*1.0*64 - DG*5.3*926 be installed prior to RG*1.0*65 Therefore non-legacy sites can install FB*3.5*173 and DG*5.3*926 in any order, then install MPIF*1.0*64 and RG*1.0*65 patches in any order (Do NOT install MPIF*1.0*64 or RG*1.0*65 on legacy sites). NOTE: Legacy sites can install just the DG*5.3*926 and FB*3.5*173 patches. MPIF*1.0*64 and RG*1.0*65 should NOT be installed on legacy sites. Enhancement This enhancement patch provides additional support to allow the Master Veteran Index (MVI) to support the Date of Death of patients at the medical facilities. Enhancement #1 A new remote procedure (RPC) [MPIF DOD ACTIVITY CHECK] was created to search through various packages: FEE BASIS, OUTPATIENT PHARMACY, PCE PATIENT CARE ENCOUNTER, REGISTRAION and SCHEDULING, to find any activity that might indicate that a patient is not actually deceased. The validity of the reported Date of Death will be confirmed if no activity is found. Routine MPIFDODC was created to support the functionality in this RPC. Enhancement #2 Routine MPIFA31B was updated to build and retrieve the parsed OBX A31 Health Level Seven (HL7) Patient update message segments for the following additional Date of Death fields in the PATIENT (#2) file: - DATE OF DEATH LAST UPDATED (#.354) - SUPPORTING DOCUMENT TYPE (#.357) - DATE OF DEATH OPTION USED (#.358) Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------------- -------------------- MPIF DOD ACTIVITY CHECK NEW Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A Remedy Ticket(s) & Overview --------------------------- N/A Test Sites: ---------- Central Alabama HCS Indianapolis VAMC Louisville VAMC Software and Documentation Retrieval Instructions: ---------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext PIMS ADT Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/application.asp?appid=55 Title File Name FTP Mode --------------------------------------------------------------------------- PIMS ADT User Manual - Bed Control Menu DG_5_3_P926_BC_UM.PDF (binary) PIMS ADT User Manual - Registration Menu DG_5_3_P926_REG_UM.PDF (binary) MPI/PD VistA Documentation can also be found on the VA Software Documentation Library at: http://www.domain.ext/vdl/application.asp?appid=16 Title File Name FTP Mode --------------------------------------------------------------------------- MPI/PD VISTA User Manual RG_1_0_P65_UM.PDF (binary) MPI/PD VISTA Programmer Manual RG_1_0_P65_PM.PDF (binary) MPI/PD VISTA Technical Manual RG_1_0_P65_TM.PDF (binary) Patch Installation: Pre/Post Installation Overview ------------------------------ There are no Pre/Post installation routine processes. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Master+Patient+Index+VistA/Patches/MPIF_1.0_64

Patch Subject: MASTER VETERAN INDEX VISTA ENHANCEMENTS - ITERATION 16 RELEASE 2 Description: ============ NOTE: To prevent legacy systems ending up as Treating Facilities, RG* and MPIF* patches should NOT be installed on legacy systems. RG*1.0*63 and DG*5.3*926 are the required builds for patch RG*1.0*65. NOTE: Master Patient Index (MPI) enhancements are being distributed in four VistA namespaces: DG, MPIF, RG and FB. The only build enforced requirements are that: - FB*3.5*173 and DG*5.3*926 be installed prior to MPIF*1.0*64 - DG*5.3*926 be installed prior to RG*1.0*65 Therefore non-legacy sites can install FB*3.5*173 and DG*5.3*926 in any order, then install MPIF*1.0*64 and RG*1.0*65 patches in any order (Do NOT install MPIF*1.0*64 or RG*1.0*65 on legacy sites). NOTE: Legacy sites can install just the DG*5.3*926 and FB*3.5*173 patches. MPIF*1.0*64 and RG*1.0*65 should NOT be installed on legacy sites. Enhancement This enhancement patch provides additional support to allow the Master Veteran Index (MVI) to support the Date of Death of patients at the medical facilities. Enhancement #1 Routine RGADTP was updated to build and retrieve the parsed OBX A08 Health Level Seven (HL7) Patient update message segments for the following additional Date of Death fields in the PATIENT (#2) file: - DATE OF DEATH LAST UPDATED (#.354) - SUPPORTING DOCUMENT TYPE (#.357) - DATE OF DEATH OPTION USED (#.358) Enhancement #2 Routine RGADPT was also modified at the GENACK tag entry point, where the Application Acknowledgement (AA) to the MPI is built, to pass the name and current value of the PROCESS MVI DOD UPDATE? (#1401) field in the MAS PARAMETERS (#43) file, utilizing the $$CHK^VAFCDODA() application programming interface (API). Note: MPI will use this value to determine if all of the Date of Death information should be sync'd out to the site. Enhancement #3 Routine RGADTP3 was modified to update the following Date of Death fields in the PATIENT (#2) file: - DATE OF DEATH (#.351) - DEATH ENTERED BY (#.352) - SOURCE OF NOTIFICATION (#.353) - DATE OF DEATH LAST UPDATED (#.354) - LAST EDITED BY (#.355) - SUPPORTING DOCUMENT TYPE (#.357) - DATE OF DEATH OPTION USED (#.358) Enhancement #4 Routines RGADTP and RGADTP3 were also modified to allow VistA to ignore all updates to the Date of Death fields if an imprecise Date of Death is passed. In addition, VistA will transmit an imprecise flag back to the MVI in the Application Acknowledgement (AA) synchronization message, which will allow MVI to ignore the Date of Death field updates in that particular correlation. Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Remote Procedure Calls (RPC) Associated: RPC Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A Remedy Ticket(s) & Overview --------------------------- N/A Test Sites: ---------- Central Alabama HCS Indianapolis VAMC Louisville VAMC Software and Documentation Retrieval Instructions: ---------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext PIMS ADT Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/application.asp?appid=55 Title File Name FTP Mode --------------------------------------------------------------------------- PIMS ADT User Manual - Bed Control Menu DG_5_3_P926_BC_UM.PDF (binary) PIMS ADT User Manual - Registration Menu DG_5_3_P926_REG_UM.PDF (binary) MPI/PD VistA Documentation can also be found on the VA Software Documentation Library at: http://www.domain.ext/vdl/application.asp?appid=16 Title File Name FTP Mode --------------------------------------------------------------------------- MPI/PD VISTA User Manual RG_1_0_P65_UM.PDF (binary) MPI/PD VISTA Programmer Manual RG_1_0_P65_PM.PDF (binary) MPI/PD VISTA Technical Manual RG_1_0_P65_TM.PDF (binary) Patch Installation: Pre/Post Installation Overview ------------------------------ There are no Pre/Post installation routine processes. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Clinical+Information+Resource+Network/Patches/RG_1.0_65

Patch Subject: PCE IMMUNIZATION ENHANCEMENTS - INCREMENT 4 Description: ============ The Veterans Health Information Systems and Technology Architecture (VistA) Immunizations Enhancements (VIMM) 2.0 project, Increment 4, builds upon the file structures and standardized data introduced in Increments 1, 2 and 3 by adding functional enhancements to the existing VistA Patient Care Encounter (PCE) package. This patch provides the following new features: 1) Introduces a new file, V IMMUNIZATION DELETED (#9000080.11), that will contain entries that were deleted out of the V IMMUNIZATION file (#9000010.11). Immediately prior to deleting an entry from the V IMMUNIZATION file, a copy of the record will be made and filed to the V IMMUNIZATION DELETED file. The date/time of deletion and the user that deleted the record will be recorded. 2) Creates Remote Procedure Calls (RPCs) for use by the Enterprise Health Management Platform (eHMP) project, the Computerized Patient Record System (CPRS) software and others. These RPCs retrieve skin test information from the following files: - V SKIN TEST (#9000010.12) - SKIN TEST (#9999999.28) - IMM ADMINISTRATION SITE (BODY) (#920.3) 3) Creates a RPC to retrieve immunization data from the V IMMUNIZATION (#9000010.11) file. This data will be used in the future to retrieve patient immunization data and transmit it, using the Health Level 7 (HL7) standard protocol, to external agencies (e.g., State Immunization Information Registries). As part of this effort, a new option will be introduced with this patch, Accounting Of Immunization Disclosures Report [PXV IMM DISCLOSURE REPORT], that can be run from the PCE Coordinator Menu [PX PCE COORDINATOR MENU]. This option can be used to generate a list of immunization records transmitted to external agencies. This option allows for a date range selection as well as one, multiple or all agencies and one, multiple or all patients. 4) Previously, auditing has been turned on for all fields of the V IMMUNIZATION (#9000010.11) file. Additional safe guards are added to ensure auditing is not turned off and the data audits cannot be purged for the V IMMUNIZATION file. 5) The existing immunization inventory functionality is updated to include multi-divisional features: - Inventory items may be linked to an associated facility. - Inventory reports are facility specific. 6) The immunization entry process is updated to require the entry of Dose, Dose Units, Route of Administration and Site of Administration (Note: If route is ORAL, site is not required.). 7) The PX SAVE DATA remote procedure call (RPC) has been modified to provide support for the following fields in the V SKIN TEST file (#9000010.12): - READER (#.07) - ORDERING PROVIDER (#1202) - ANATOMIC LOCATION OF PLACEMENT (#1212) - READING COMMENTS (#1301) 8) The functionality for the Health Summary component PCE IMMUNIZATIONS (IM) is modified to ignore time and occurrence limits, basically restoring pre-patch PX*1*210 behavior. 9) Provides an alert whenever specific allergy-type contraindications are recorded, as a reason for not giving an immunization, in the V IMM CONTRA/REFUSAL EVENTS file (#9000010.707). The alert text reads: "You have recorded an allergy/adverse reaction contraindication reason. This information should also be recorded in the Adverse Reaction Tracking package if it is not already present there." Patch Components: ----------------- APIs Associated: API New/Modified/Deleted ----------- -------------------- VSKIN^PXPXRM (ICR #4250) Modified Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- IMM EXTERNAL AGENCY AGENCY NAME (#.01) New (#920.71) V IMMUNIZATION IMMUNIZATION (#.01) Modified (#9000010.11) EVENT DATE AND TIME Modified (#1201) DATE/TIME RECORDED Modified (#1205) TIMESTAMP (#1221) New EVENT INFORMATION Modified SOURCE (#1301) DISCLOSED TO (multiple New (field #820, sub-file #9000010.1182) AGENCY (#.01) of the New DISCLOSED TO sub-file (#9000010.1182) DISCLOSURE DATE/TIME New (#.02) of the DISCLOSED TO sub-file (#9000010.1182) IMMUNIZATION LOT LOT NUMBER (#.01) Modified (#9999999.41) MANUFACTURER (#.02) Modified VACCINE (#.04) Modified ASSOCIATED VA FACILITY New (#.1) V IMMUNIZATION DELETED (#9000080.11) IMMUNIZATION (#.01) New PATIENT NAME (#.02) New VISIT (#.03) New SERIES (#.04) New LOT (#.05) ) New REACTION (#.06) New CONTRAINDICATED (#.07) New DOSE OVERRIDE (#.08) New INJECTION SITE (#.09) New VOLUME (#.11) New DATE OF VAC INFO STATEMENT (#.12) New CREATED BY V CPT ENTRY (#.13) New VAC ELIGIBILITY (#.14) New IMPORT FROM OUTSIDE REGISTRY New (#.15) NDC (#.16) New ADMINISTRATIVE NOTES (#1) New VIS OFFERED/GIVEN TO PATIENT (multiple field #2, sub-file #9000080.112) New VIS OFFERED/GIVEN TO PATIENT (#.01) of the VIS OFFERED/GIVEN TO PATIENT sub-file (#9000080.112) New DATE VIS OFFERED/GIVEN (#.02) of the VIS OFFERED/GIVEN TO PATIENT sub-file (#9000080.112) New OTHER DIAGNOSIS (multiple field #3, sub-file #9000080.113) New OTHER DIAGNOSIS (#.01) of the OTHER DIAGNOSIS sub-file (#9000080.113) New REMARKS (#1101) New EVENT DATE AND TIME (#1201) New ORDERING PROVIDER (#1202) New CLINIC (#1203) New ENCOUNTER PROVIDER (#1204) New DATE/TIME RECORDED (#1205) New IMMUNIZATION DOCUMENTER (#1206) New LOT NUMBER (#1207) New PARENT (#1208) New EXTERNAL KEY (#1209) New OUTSIDE PROVIDER NAME (#1210) New ANCILLARY POV (#1213) New USER LAST UPDATE (#1214) New ORDERING LOCATION (#1215) New DATE/TIME ENTERED (#1216) New ENTERED BY (#1217) New DATE/TIME LAST MODIFIED (#1218) New LAST MODIFIED BY (#1219) New WARNING ACKNOWLEDGED (#1220) New EVENT INFORMATION SOURCE (#1301) New ROUTE OF ADMINISTRATION (#1302) New SITE OF ADMINISTRATION (BODY) (#1303) New PRIMARY DIAGNOSIS (#1304) New DOSE (#1312) New DOSAGE (#1312.5) New DOSE UNITS (#1313) New SNOMED CT (multiple field #2601, sub-file #9000080.1126) New SNOMED CT (#.01) of the SNOMED CT sub-file (#9000080.1126) New SNOMED PREFERRED TERM (#.019) of the SNOMED CT sub-file (#9000080.1126) New LOINC CODES (multiple field #2701, sub-file #9000080.1127) New LOINC CODES (#.01) of the LOINC CODES sub-file (#9000080.1127) New LOINC TEXT (#.019) of the LOINC CODES sub-file (#9000080.1127) New RESULTS (#1401) New READING (#1402) New DATE/TIME READ (#1403) New READER (#1404) New READING RECORDED (#1405) New HOURS READ POST-INOCULATION (#1406) New READING COMMENT (#1501) New WARNING OVERRIDE REASON (#1601) New EDITED FLAG (#80101) New AUDIT TRAIL (#80102) New COMMENTS (#81101) New VERIFIED (#81201) New PACKAGE (#81202) New DATA SOURCE (#81203) New DISCLOSED TO (multiple New (field #820, sub-file #9000080.1182) AGENCY (#.01) of the New DISCLOSED TO sub-file (#9000080.1182) DISCLOSURE DATE/TIME New (#.02) of the DISCLOSED TO sub-file (#9000080.1182) DELETED BY (#88001) New DATE/TIME DELETED (#88002) New Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- PXV IMM DISCLOSURE REPORT Run Routine New Parameters Associated: Parameter Definition Name New/Modified/Deleted ------------------------- -------------------- PXV SK DAYS BACK New Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- RPCs Associated: RPC New/Modified/Deleted ------------- -------------------- PXVIMM ICR LIST Modified PXVIMM IMM DETAILED Modified PXVIMM IMM DISCLOSURE New PXVIMM IMM LOT Modified PXVIMM VIMM DATA New PXVSK DEF SITES New PXVSK SKIN SHORT LIST New PXVSK V SKIN TEST LIST New PX SAVE DATA Modified Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: ----------------------- N/A New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- N/A Test Sites: ---------- Cleveland, OH Heartland-East HCS, MO San Antonio, TX Software and Documentation Retrieval Instructions: ---------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ Title File Name FTP Mode ------------------------------------------------------------------ Patient Care Encounter (PCE) PX_1_UM_R1016.PDF (binary) V. 1.0 User Manual Patient Care Encounter (PCE) PX_1_TM_R1016.PDF (binary) V.1.0 Technical Manual VIMM Patch PX*1*216 PX_1_P216_IG.PDF (binary) Installation Guide Patch Installation: Pre/Post Installation Overview: ------------------------------- The pre-installation process deletes the trigger cross-reference from the EVENT DATE AND TIME (#1201) field of the V IMMUNIZATION (#9000010.11) file. The trigger will be moved to the IMMUNIZATION (#.01) field. The trigger sets the DATE/TIME RECORDED (#1205) field. The post-installation process sets a node in the V IMMUNIZATION data dictionary (DD) that prevents a user from being able to purge data audits for the V IMMUNIZATION file. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/PCE+Patient+Care+Encounter/Patches/PX_1.0_216

Patch Subject: MASTER VETERAN INDEX VISTA ENHANCEMENTS - ITERATION 16 RELEASE 2 Description: ============ ************************************************************************* * This patch may be installed with users on the system, however we * * strongly advise it be installed after business hours. * ************************************************************************* NOTE: To prevent legacy systems ending up as Treating Facilities, RG* and MPIF* patches should NOT be installed on legacy systems. MPIF*1.0*60, DG*5.3*926 and FB*3.5*173 are the required builds for patch MPIF*1.0*64. NOTE: Master Patient Index (MPI) enhancements are being distributed in four VistA namespaces: DG, MPIF, RG and FB. The only build enforced requirements are that: - FB*3.5*173 and DG*5.3*926 be installed prior to MPIF*1.0*64 - DG*5.3*926 be installed prior to RG*1.0*65 Therefore non-legacy sites can install FB*3.5*173 and DG*5.3*926 in any order, then install MPIF*1.0*64 and RG*1.0*65 patches in any order (Do NOT install MPIF*1.0*64 or RG*1.0*65 on legacy sites). NOTE: Legacy sites can install just the DG*5.3*926 and FB*3.5*173 patches. MPIF*1.0*64 and RG*1.0*65 should NOT be installed on legacy sites. Enhancement This enhancement patch provides additional support to allow the Master Veteran Index (MVI) to support the Date of Death of patients at the medical facilities. Enhancement #1 A new remote procedure (RPC) [MPIF DOD ACTIVITY CHECK] was created to search through various packages: FEE BASIS, OUTPATIENT PHARMACY, PCE PATIENT CARE ENCOUNTER, REGISTRAION and SCHEDULING, to find any activity that might indicate that a patient is not actually deceased. The validity of the reported Date of Death will be confirmed if no activity is found. Routine MPIFDODC was created to support the functionality in this RPC. Enhancement #2 Routine MPIFA31B was updated to build and retrieve the parsed OBX A31 Health Level Seven (HL7) Patient update message segments for the following additional Date of Death fields in the PATIENT (#2) file: - DATE OF DEATH LAST UPDATED (#.354) - SUPPORTING DOCUMENT TYPE (#.357) - DATE OF DEATH OPTION USED (#.358) Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------------- -------------------- MPIF DOD ACTIVITY CHECK NEW Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A Remedy Ticket(s) & Overview --------------------------- N/A Test Sites: ---------- Central Alabama HCS Indianapolis VAMC Louisville VAMC Software and Documentation Retrieval Instructions: ---------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext PIMS ADT Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/application.asp?appid=55 Title File Name FTP Mode --------------------------------------------------------------------------- PIMS ADT User Manual - Bed Control Menu DG_5_3_P926_BC_UM.PDF (binary) PIMS ADT User Manual - Registration Menu DG_5_3_P926_REG_UM.PDF (binary) MPI/PD VistA Documentation can also be found on the VA Software Documentation Library at: http://www.domain.ext/vdl/application.asp?appid=16 Title File Name FTP Mode --------------------------------------------------------------------------- MPI/PD VISTA User Manual RG_1_0_P65_UM.PDF (binary) MPI/PD VISTA Programmer Manual RG_1_0_P65_PM.PDF (binary) MPI/PD VISTA Technical Manual RG_1_0_P65_TM.PDF (binary) Patch Installation: Pre/Post Installation Overview ------------------------------ There are no Pre/Post installation routine processes. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Master+Patient+Index+VistA/Patches/MPIF_1.0_64

Patch Subject: MASTER VETERAN INDEX VISTA ENHANCEMENTS - ITERATION 16 RELEASE 2 Description: ============ NOTE: To prevent legacy systems ending up as Treating Facilities, RG* and MPIF* patches should NOT be installed on legacy systems. RG*1.0*63 and DG*5.3*926 are the required builds for patch RG*1.0*65. NOTE: Master Patient Index (MPI) enhancements are being distributed in four VistA namespaces: DG, MPIF, RG and FB. The only build enforced requirements are that: - FB*3.5*173 and DG*5.3*926 be installed prior to MPIF*1.0*64 - DG*5.3*926 be installed prior to RG*1.0*65 Therefore non-legacy sites can install FB*3.5*173 and DG*5.3*926 in any order, then install MPIF*1.0*64 and RG*1.0*65 patches in any order (Do NOT install MPIF*1.0*64 or RG*1.0*65 on legacy sites). NOTE: Legacy sites can install just the DG*5.3*926 and FB*3.5*173 patches. MPIF*1.0*64 and RG*1.0*65 should NOT be installed on legacy sites. Enhancement This enhancement patch provides additional support to allow the Master Veteran Index (MVI) to support the Date of Death of patients at the medical facilities. Enhancement #1 Routine RGADTP was updated to build and retrieve the parsed OBX A08 Health Level Seven (HL7) Patient update message segments for the following additional Date of Death fields in the PATIENT (#2) file: - DATE OF DEATH LAST UPDATED (#.354) - SUPPORTING DOCUMENT TYPE (#.357) - DATE OF DEATH OPTION USED (#.358) Enhancement #2 Routine RGADPT was also modified at the GENACK tag entry point, where the Application Acknowledgement (AA) to the MPI is built, to pass the name and current value of the PROCESS MVI DOD UPDATE? (#1401) field in the MAS PARAMETERS (#43) file, utilizing the $$CHK^VAFCDODA() application programming interface (API). Note: MPI will use this value to determine if all of the Date of Death information should be sync'd out to the site. Enhancement #3 Routine RGADTP3 was modified to update the following Date of Death fields in the PATIENT (#2) file: - DATE OF DEATH (#.351) - DEATH ENTERED BY (#.352) - SOURCE OF NOTIFICATION (#.353) - DATE OF DEATH LAST UPDATED (#.354) - LAST EDITED BY (#.355) - SUPPORTING DOCUMENT TYPE (#.357) - DATE OF DEATH OPTION USED (#.358) Enhancement #4 Routines RGADTP and RGADTP3 were also modified to allow VistA to ignore all updates to the Date of Death fields if an imprecise Date of Death is passed. In addition, VistA will transmit an imprecise flag back to the MVI in the Application Acknowledgement (AA) synchronization message, which will allow MVI to ignore the Date of Death field updates in that particular correlation. Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Remote Procedure Calls (RPC) Associated: RPC Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A Remedy Ticket(s) & Overview --------------------------- N/A Test Sites: ---------- Central Alabama HCS Indianapolis VAMC Louisville VAMC Software and Documentation Retrieval Instructions: ---------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext PIMS ADT Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/application.asp?appid=55 Title File Name FTP Mode --------------------------------------------------------------------------- PIMS ADT User Manual - Bed Control Menu DG_5_3_P926_BC_UM.PDF (binary) PIMS ADT User Manual - Registration Menu DG_5_3_P926_REG_UM.PDF (binary) MPI/PD VistA Documentation can also be found on the VA Software Documentation Library at: http://www.domain.ext/vdl/application.asp?appid=16 Title File Name FTP Mode --------------------------------------------------------------------------- MPI/PD VISTA User Manual RG_1_0_P65_UM.PDF (binary) MPI/PD VISTA Programmer Manual RG_1_0_P65_PM.PDF (binary) MPI/PD VISTA Technical Manual RG_1_0_P65_TM.PDF (binary) Patch Installation: Pre/Post Installation Overview ------------------------------ There are no Pre/Post installation routine processes. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Clinical+Information+Resource+Network/Patches/RG_1.0_65

Patch Subject: PCE IMMUNIZATION ENHANCEMENTS - INCREMENT 4 Description: ============ The Veterans Health Information Systems and Technology Architecture (VistA) Immunizations Enhancements (VIMM) 2.0 project, Increment 4, builds upon the file structures and standardized data introduced in Increments 1, 2 and 3 by adding functional enhancements to the existing VistA Patient Care Encounter (PCE) package. This patch provides the following new features: 1) Introduces a new file, V IMMUNIZATION DELETED (#9000080.11), that will contain entries that were deleted out of the V IMMUNIZATION file (#9000010.11). Immediately prior to deleting an entry from the V IMMUNIZATION file, a copy of the record will be made and filed to the V IMMUNIZATION DELETED file. The date/time of deletion and the user that deleted the record will be recorded. 2) Creates Remote Procedure Calls (RPCs) for use by the Enterprise Health Management Platform (eHMP) project, the Computerized Patient Record System (CPRS) software and others. These RPCs retrieve skin test information from the following files: - V SKIN TEST (#9000010.12) - SKIN TEST (#9999999.28) - IMM ADMINISTRATION SITE (BODY) (#920.3) 3) Creates a RPC to retrieve immunization data from the V IMMUNIZATION (#9000010.11) file. This data will be used in the future to retrieve patient immunization data and transmit it, using the Health Level 7 (HL7) standard protocol, to external agencies (e.g., State Immunization Information Registries). As part of this effort, a new option will be introduced with this patch, Accounting Of Immunization Disclosures Report [PXV IMM DISCLOSURE REPORT], that can be run from the PCE Coordinator Menu [PX PCE COORDINATOR MENU]. This option can be used to generate a list of immunization records transmitted to external agencies. This option allows for a date range selection as well as one, multiple or all agencies and one, multiple or all patients. 4) Previously, auditing has been turned on for all fields of the V IMMUNIZATION (#9000010.11) file. Additional safe guards are added to ensure auditing is not turned off and the data audits cannot be purged for the V IMMUNIZATION file. 5) The existing immunization inventory functionality is updated to include multi-divisional features: - Inventory items may be linked to an associated facility. - Inventory reports are facility specific. 6) The immunization entry process is updated to require the entry of Dose, Dose Units, Route of Administration and Site of Administration (Note: If route is ORAL, site is not required.). 7) The PX SAVE DATA remote procedure call (RPC) has been modified to provide support for the following fields in the V SKIN TEST file (#9000010.12): - READER (#.07) - ORDERING PROVIDER (#1202) - ANATOMIC LOCATION OF PLACEMENT (#1212) - READING COMMENTS (#1301) 8) The functionality for the Health Summary component PCE IMMUNIZATIONS (IM) is modified to ignore time and occurrence limits, basically restoring pre-patch PX*1*210 behavior. 9) Provides an alert whenever specific allergy-type contraindications are recorded, as a reason for not giving an immunization, in the V IMM CONTRA/REFUSAL EVENTS file (#9000010.707). The alert text reads: "You have recorded an allergy/adverse reaction contraindication reason. This information should also be recorded in the Adverse Reaction Tracking package if it is not already present there." Patch Components: ----------------- APIs Associated: API New/Modified/Deleted ----------- -------------------- VSKIN^PXPXRM (ICR #4250) Modified Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- IMM EXTERNAL AGENCY AGENCY NAME (#.01) New (#920.71) V IMMUNIZATION IMMUNIZATION (#.01) Modified (#9000010.11) EVENT DATE AND TIME Modified (#1201) DATE/TIME RECORDED Modified (#1205) TIMESTAMP (#1221) New EVENT INFORMATION Modified SOURCE (#1301) DISCLOSED TO (multiple New (field #820, sub-file #9000010.1182) AGENCY (#.01) of the New DISCLOSED TO sub-file (#9000010.1182) DISCLOSURE DATE/TIME New (#.02) of the DISCLOSED TO sub-file (#9000010.1182) IMMUNIZATION LOT LOT NUMBER (#.01) Modified (#9999999.41) MANUFACTURER (#.02) Modified VACCINE (#.04) Modified ASSOCIATED VA FACILITY New (#.1) V IMMUNIZATION DELETED (#9000080.11) IMMUNIZATION (#.01) New PATIENT NAME (#.02) New VISIT (#.03) New SERIES (#.04) New LOT (#.05) ) New REACTION (#.06) New CONTRAINDICATED (#.07) New DOSE OVERRIDE (#.08) New INJECTION SITE (#.09) New VOLUME (#.11) New DATE OF VAC INFO STATEMENT (#.12) New CREATED BY V CPT ENTRY (#.13) New VAC ELIGIBILITY (#.14) New IMPORT FROM OUTSIDE REGISTRY New (#.15) NDC (#.16) New ADMINISTRATIVE NOTES (#1) New VIS OFFERED/GIVEN TO PATIENT (multiple field #2, sub-file #9000080.112) New VIS OFFERED/GIVEN TO PATIENT (#.01) of the VIS OFFERED/GIVEN TO PATIENT sub-file (#9000080.112) New DATE VIS OFFERED/GIVEN (#.02) of the VIS OFFERED/GIVEN TO PATIENT sub-file (#9000080.112) New OTHER DIAGNOSIS (multiple field #3, sub-file #9000080.113) New OTHER DIAGNOSIS (#.01) of the OTHER DIAGNOSIS sub-file (#9000080.113) New REMARKS (#1101) New EVENT DATE AND TIME (#1201) New ORDERING PROVIDER (#1202) New CLINIC (#1203) New ENCOUNTER PROVIDER (#1204) New DATE/TIME RECORDED (#1205) New IMMUNIZATION DOCUMENTER (#1206) New LOT NUMBER (#1207) New PARENT (#1208) New EXTERNAL KEY (#1209) New OUTSIDE PROVIDER NAME (#1210) New ANCILLARY POV (#1213) New USER LAST UPDATE (#1214) New ORDERING LOCATION (#1215) New DATE/TIME ENTERED (#1216) New ENTERED BY (#1217) New DATE/TIME LAST MODIFIED (#1218) New LAST MODIFIED BY (#1219) New WARNING ACKNOWLEDGED (#1220) New EVENT INFORMATION SOURCE (#1301) New ROUTE OF ADMINISTRATION (#1302) New SITE OF ADMINISTRATION (BODY) (#1303) New PRIMARY DIAGNOSIS (#1304) New DOSE (#1312) New DOSAGE (#1312.5) New DOSE UNITS (#1313) New SNOMED CT (multiple field #2601, sub-file #9000080.1126) New SNOMED CT (#.01) of the SNOMED CT sub-file (#9000080.1126) New SNOMED PREFERRED TERM (#.019) of the SNOMED CT sub-file (#9000080.1126) New LOINC CODES (multiple field #2701, sub-file #9000080.1127) New LOINC CODES (#.01) of the LOINC CODES sub-file (#9000080.1127) New LOINC TEXT (#.019) of the LOINC CODES sub-file (#9000080.1127) New RESULTS (#1401) New READING (#1402) New DATE/TIME READ (#1403) New READER (#1404) New READING RECORDED (#1405) New HOURS READ POST-INOCULATION (#1406) New READING COMMENT (#1501) New WARNING OVERRIDE REASON (#1601) New EDITED FLAG (#80101) New AUDIT TRAIL (#80102) New COMMENTS (#81101) New VERIFIED (#81201) New PACKAGE (#81202) New DATA SOURCE (#81203) New DISCLOSED TO (multiple New (field #820, sub-file #9000080.1182) AGENCY (#.01) of the New DISCLOSED TO sub-file (#9000080.1182) DISCLOSURE DATE/TIME New (#.02) of the DISCLOSED TO sub-file (#9000080.1182) DELETED BY (#88001) New DATE/TIME DELETED (#88002) New Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- PXV IMM DISCLOSURE REPORT Run Routine New Parameters Associated: Parameter Definition Name New/Modified/Deleted ------------------------- -------------------- PXV SK DAYS BACK New Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- RPCs Associated: RPC New/Modified/Deleted ------------- -------------------- PXVIMM ICR LIST Modified PXVIMM IMM DETAILED Modified PXVIMM IMM DISCLOSURE New PXVIMM IMM LOT Modified PXVIMM VIMM DATA New PXVSK DEF SITES New PXVSK SKIN SHORT LIST New PXVSK V SKIN TEST LIST New PX SAVE DATA Modified Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: ----------------------- N/A New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- N/A Test Sites: ---------- Cleveland, OH Heartland-East HCS, MO San Antonio, TX Software and Documentation Retrieval Instructions: ---------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ Title File Name FTP Mode ------------------------------------------------------------------ Patient Care Encounter (PCE) PX_1_UM_R1016.PDF (binary) V. 1.0 User Manual Patient Care Encounter (PCE) PX_1_TM_R1016.PDF (binary) V.1.0 Technical Manual VIMM Patch PX*1*216 PX_1_P216_IG.PDF (binary) Installation Guide Patch Installation: Pre/Post Installation Overview: ------------------------------- The pre-installation process deletes the trigger cross-reference from the EVENT DATE AND TIME (#1201) field of the V IMMUNIZATION (#9000010.11) file. The trigger will be moved to the IMMUNIZATION (#.01) field. The trigger sets the DATE/TIME RECORDED (#1205) field. The post-installation process sets a node in the V IMMUNIZATION data dictionary (DD) that prevents a user from being able to purge data audits for the V IMMUNIZATION file. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/PCE+Patient+Care+Encounter/Patches/PX_1.0_216

Patch Subject: FIX INCORRECT MSE PROMPTS Description: ============ ************************************************************************** Note: DG*5.3*855 is being released along with IVM*2*153 (Income Verification Match) in host file: DG_53_P855.KID. It is imperative that these patches be installed no later than the compliance date. Your understanding and support is appreciated. ************************************************************************** Patch DG*5.3*797 added the new MILITARY SERVICE EPISODE sub-file #2.3216 in the PATIENT (#2) file to store Military Service Episode (MSE) data. Changes in that patch included modifications to several consistency checks that used MSE data. The consistency checks that are listed in the DG*5.3*797 patch description are correctly using the new MILITARY SERVICE EPISODE sub-file #2.3216 and the new Screen 6.1 to edit the data. However, there is a set of consistency checks in the INCONSISTENT DATA ELEMENTS (#38.6) file that are considered related to Eligibility. If any of those inconsistencies are edited; the user is prompted with a set of eligibility-related fields that include the Last Service Episode fields. Since these inconsistencies were not modified for DG*5.3*797, the user is being prompted with the old MSE fields for SERVICE EPISODE [LAST]. These are the inconsistencies that are considered related to Eligibility: 9 VETERAN STATUS UNSPECIFIED 10 SC PROMPT UNANSWERED 11 SC PROMPT INCONSISTENT 12 SC% UNSPECIFIED FOR SC VET 13 POS UNSPECIFIED 14 ELIG CODE UNSPECIFIED 18 ELIG/VET STATUS INCONSISTENT 19 ELIG/NONVET STAT INCONSISTENT 20 ELIG/SC% INCONSISTENT 22 ELIG CODE INCONSISTENT 24 POS/ELIG CODE INCONSISTENT 36 PATIENT TYPE UNDEFINED This patch is being released with patch IVM*2.0*153 in host file DG_53_P855.KID. ASSOCIATED TICKETS: =================== 1.) INC000000623739 -DG*5.3*797 - MSDS MSE inappropriate prompts I9915503FY16(d) INC000000759547(d) I9914518FY16(d) ASSOCIATED NSR: =============== N/A PARTICIPATING TEST SITES: ========================= Tuscaloosa VA Medical Center Upstate New York Health Care System West Palm Beach VA Medical Center Ticket Overview: ================= 1.)INC000000623739 - DG*5.3*797 - MSDS MSE inappropriate prompts I9915503FY16(d) INC000000759547(d) I9914518FY16(d) Problem: -------- There is a set of consistency checks in the INCONSISTENT DATA ELEMENTS (#38.6) file that are considered related to Eligibility. If any of those inconsistencies are edited; the user is prompted with a set of eligibility-related fields that include the Last Service Episode fields. Since these inconsistencies were not modified for DG*5.3*797, the user is being prompted with the old MSE fields for SERVICE EPISODE [LAST]. These are the inconsistencies that are considered related to Eligibility: 9 VETERAN STATUS UNSPECIFIED 10 SC PROMPT UNANSWERED 11 SC PROMPT INCONSISTENT 12 SC% UNSPECIFIED FOR SC VET 13 POS UNSPECIFIED 14 ELIG CODE UNSPECIFIED 18 ELIG/VET STATUS INCONSISTENT 19 ELIG/NONVET STAT INCONSISTENT 20 ELIG/SC% INCONSISTENT 22 ELIG CODE INCONSISTENT 24 POS/ELIG CODE INCONSISTENT 36 PATIENT TYPE UNDEFINED Resolution: ----------- Routines DGRPCE and DGRPCE1 are being edited to allow users to edit the new MSE data in sub-file #2.3216 on the new screen 6.1, with any of the eligibility-related inconsistencies. Use default answers for KIDS load/install questions. Multi-Build: http://code.osehra.org/VistA.git/blob/master/Packages/Registration/Patches/DG_5.3_855/DG_53_P855.KID

Patch Subject: EXTENSIBLE DATA TYPES AND META DD EHNANCEMENTS Description: ============ The Veterans Information Systems and Technology Architecture (VistA) Evolution program to modernize VistA includes modernizing Veterans Affairs (VA's) enterprise data management capabilities. Modernizing FileMan will functionally standardize VistA's database. This will enable structured data query and exchange across all VistA instances, creating an enterprise view of VistA data in standardized, computable form. This modernized FileMan is called FileMan Enterprise for its enterprise data management capabilities. This specific patch contains new datatypes for FileMan 22.2 as well as enhancements to the FileMan Meta Data Dictionary. 1. This build introduces the following new data types: a. BOOLEAN: A version of the SET data type with only two entry choices - TRUE or FALSE. b. MUMPS LABEL: A version of the FREETEXT data type that allows the storage of a tag and routine entry of the format, TAG^ROUTINE. c. TIME: Allows the input of date/time entries but will only store the TIME portion of the user input. d. YEAR: Allows the input of date/time entries but will only store the YEAR portion of the user input. e. FT DATE: Similar to the DATE/TIME DATA TYPE but internally stores the free text that was inputted by the user to determine the date. f. FT POINTER: Similar to the POINTER data type but internally stores the external value of the pointed to field. g. UNIVERSAL TIME: Allows the input of date/time entries and stores the Greenwich Mean Time in normal date/time format but also includes the offset from the current timezone. h. RATIO: Accept two numbers with a colon (":") between the two numbers. It is formatted and stored like a mathematical ratio. When defining a field with a DATA TYPE of RATIO the user will be asked for the minimum and maximum of each number in the ratio. 2. A new FileMan API (UTC^DIUTC) was created that allows the conversion of an internal FileMan date/time into Greenwich Mean Time and offset. The API needs to know the location, which is done by passing the Country and Timezone as input parameters, passing an Institution as a parameter (which has country and timezone fields defined), or using the Institution derived by the default Institution setup for the user. 3. The FileMan Meta Data Dictionary provides each site's specification of the FileMan files, the associated FileMan fields within each of those files, and descriptive metadata about the site data for each individual VistA instance. This patch adds functionality to do partial updates (deltas) to the Meta Data Dictionary. Patch Components: ----------------- Files & Fields Associated: File Name (#) New/Modified/ Sub-file Name (#) Field Name (#) Deleted ------------------- ----------------------------- ------------- DATA TYPE (#.81) NUMBER (#.001) New NAME (#.01) Modified INTERNAL REPRESENTATION (#1) Modified STANDARD PROMPT (#2) New SORT BY EXTERNAL (#3) New SHORT DESCRIPTION (#11) New DESCRIPTION (#21) New FIELDS DEFINED BY THIS TYPE (#41) New FIELD DEFINED BY THIS TYPE (#.01) New PROPERTY (#101) New PROPERTY (#.01) New ORDER (#1) New PROMPT? (#10) New VALUE (#31) New DEFAULT VALUE PROMPTED (#33) New METHOD (#201) New METHOD (#.01) New M CODE (#31) New DATA TYPE PROPERTY (#.86) NUMBER (#.001) New NAME (#.01) New ABBREVIATION (#1) New SHORT DESCRIPTION (#11) New DESCRIPTION (#21) New DATA TYPE (#41) New DIR(0) (#42) New DATA TYPE METHODS (#.87) NUMBER (#.001) New NAME (#.01) New SHORT DESCRIPTION (#11) New DESCRIPTION (#21) New META DATA DICTIONARY (#.9) NAME (#.01) Modified OBJECT NAME (#.06) Modified LAST UPDATED (#.07) New WORLD TIMEZONES (#1.71) NAME (#.01) New TIMEFRAME (#1) New TIMEFRAME (#.01) New OFFSET (#.02) New CODE (#.03) New COUNTRY (#1) (multiple under TIMEFRAME) New COUNTRY (#.01) New WORLD DAYLIGHT SAVINGS (#1.72) COUNTRY (#.01) New TIME SAME AS (#.03) New YEAR (#1) New YEAR (#.01) New START DATE/TIME (#.02) New END DATE/TIME (#.03) New INSTITUTION (#4) LOCATION TIMEZONE (#800) New COUNTRY (#801) New TIMEZONE EXCEPTION (#802) New Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- DIP81S #.81 New DIP86S #.86 New DIP87S #.87 New Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- ENTER OR EDIT DATA TYPE FILE [DI DATA TYPE FILE] run routine New ENTER OR EDIT DATA TYPE METHOD FILE [DI DATA TYPE METHOD FILE] run routine New DATA TYPE OPTIONS [DI DATA TYPE OPTIONS] menu New ENTER OR EDIT DATA TYPE PROPERTY FILE [DI DATA TYPE PROPERTY FILE] run routine New Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------------- -------------------- DIP81IT INPUT DATA TYPE (#.81) New DIP86IT INPUT DATA TYPE PROPERTY (#.86) New DIP87IT INPUT DATA TYPE METHOD (#.87) New Additional Information: ----------------------- N/A New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. Ticket #I12659273FY17 Problem: -------- File attributes produce an error when retrieved by GET1^DID or FILE^DID. Resolution: ----------- Made changes to DIQGDD to properly retrieve attributes of a file. Known Anomalies --------------- 1. For ticket #I13081432FY17, DD Changes to display messages in the Input Transform using EN^DDIOL. This incident has been left open to be addressed in a future patch (DI*22.2*5). Blood Bank Clearance: --------------------- EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch DI*22.2*2 contains changes to a package referenced in ProPath standard titled: BBM Team Review of VistA Patches. This patch does not alter or modify any VistA Blood Bank software design safeguards or safety critical elements functions. RISK ANALYSIS: Changes made by patch DI*22.2*2 have no effect on Blood Bank software functionality, therefore RISK s none. Test Sites: ----------- West Palm Beach (alpha) Lebanon (alpha) Charleston (beta) Nashville (beta) North Florida/South Georgia (beta) Software and Documentation Retrieval Instructions: -------------------------------------------------- Documentation describing the new functionality introduced by this patch is available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www.domain.ext/vdl/ Title File Name SFTP Mode ----------------------------------------------------------------- FileMan 22.2 Advanced User Manual FM22_2UM2.PDF Binary FileMan 22.2 User Manual FM22_2UM1.PDF Binary FileMan 22.2 Developer Guide FM22_2DG.PDF Binary FileMan 22.2 Technical Manual FM22_2TM.PDF Binary Backout and Rollback Procedure: ------------------------------- The rollback plan for VistA applications is complex and not able to be a 'one size fits all' solution. The general strategy for VistA rollback is to repair the code with a follow-on patch. The development team recommends that sites log a CA Service Desk Manager (SDM) ticket if a patch needs to be backed-out. During the VistA Installation Procedure of the KIDS build, the installer should back up the modified routines by the use of the 'Backup a Transport Global' action (step 3a in the Installations Instructions below). The installer can restore the routines using the MailMan message that were saved prior to installing the patch. The backout procedure for data dictionary, options, forms, template, and data loads is more complex and may require the issuance of a follow-on patch to ensure all components are properly removed. Note that all rollback of all software components, including routines must be restored to their previous state at the same time and in conjunction with restoration of the data. Patch Installation: Pre/Post Installation Overview: ------------------------------- There is a post-install routine DINIT220 that will create the DATA TYPE (#.81), DATA TYPE PROPERTY (#.86), and DATA TYPE METHODS (#.87) files. This post-install should not be deleted. There are two manual steps that should be run at the end of the Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/VA+FileMan/Patches/DI_22.2_2

Patch Subject: REGISTRATION CHANGES FOR MEANINGFUL USE PREFERRED LANGUAGE CAPTURE Description: ============ This patch is part of a combined build that contains DG*5.3*887 and SD*5.3*619. The Preferred Language build components are an enhancement to the VistA Registration and Scheduling packages in support of 2014 EHR Certification of VistA for Meaningful Use. These components will be used to capture the preferred language preferences of the patient, which consist of the date/time that the patient identified his or her preferred language and the language that he or she prefers to use during a healthcare visit. This data will facilitate better treatment for the patient by allowing precise verbal communication through the use of interpreters, if necessary. This patch will: 1. Add a new multiple LANGUAGE DATE/TIME field (#7) with LANGUAGE DATE/TIME field (#.01) and PREFERRED LANGUAGE field (#.02) to the PATIENT file (#2). 2. Modify the ADDITIONAL PATIENT DEMOGRAPHIC DATA, SCREEN <1.1> to display Language Date/Time and Preferred Language. These values can be edited on this screen via the Register a Patient [DG REGISTER PATIENT], Load/Edit Patient Data [DG LOAD PATIENT DATA], and Eligibility Verification [DG ELIGIBILITY VERIFICATION] options. 3. Display Language Date/Time and Preferred Language within the Patient Inquiry [DG PATIENT INQUIRY] option and in the Patient Inquiry window of the Computerized Patient Record System (CPRS) GUI. These values are for display purposes only in these locations. 4. Add a new option to the ADT Manager Menu [DG MANAGER MENU] option called Meaningful Use Language Statistics [DG MEANINGFUL USE LANG STATS]. This option will generate a report that displays the number of active patients that have provided a response to the preferred language prompt. The report is titled 'Preferred Language Record for Active Patients'. The LANGUAGE file (#.85) is updated by VA FileMan release 22.2 (DI*22.2*0) to contain the complete set of International Organization for Standardization (ISO) standard languages. These languages are used for selection at the Preferred Language prompt during registration, in the ADDITIONAL PATIENT DEMOGRAPHIC DATA, SCREEN <1.1>, during the making of an appointment, and for display within the patient inquiry. Patch Components ================ Files & Fields Associated: File Name (#) Field Name (#) New/Modified/Deleted -------------------- -------------- -------------------- PATIENT (#2) Modified LANGUAGE DATE/TIME (sub-file)(#2.07) New LANGUAGE DATE/TIME (#.01) PREFERRED LANGUAGE (#.02) Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Functions Associated: Function Name New/Modified/Deleted ------------- -------------------- N/A HL Logical Link: HL Logical Name New/Modified/Deleted --------------- -------------------- N/A HL7 Application Parameters: HL7 Parameter Name New/Modified/Deleted ------------------ -------------------- N/A HLO Application Registry: HLO Registry Name New/Modified/Deleted ------------------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- DG MANAGER MENU menu Modified DG MEANINGFUL USE LANG STATS run routine New DG REGISTER PATIENT run routine Modified DG LOAD PATIENT DATA run routine Modified DG ELIGIBILITY VERIFICATION run routine Modified Parameter Definitions: Parameter Name New/Modified/Deleted -------------- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Remote Procedure Calls (RPCs): RPC Name New/Modified/Deleted -------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (#) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: N/A New Service Requests (NSRs): ----------------------------- 20110408-Certification of VistA for Meaningful Use Patient Safety Issues (PSIs): ------------------------------ N/A Remedy Ticket(s) & Overviews: ----------------------------- N/A Test Sites: ----------- NORTH CHICAGO, IL -VAMC WEST PALM BEACH, FL Documentation Retrieval Instructions: ------------------------------------- Updated documentation describing the new functionality introduced by this patch is available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany domain.ext Hines domain.ext Salt Lake City domain.ext The documentation will be in the form of Adobe Acrobat files. Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ File Description File Name SFTP Mode -------------------------------------------------------------------------- MUNVDE Preferred Language DG_5_3_887_Install_Guide.pdf (binary) Installation Guide MUNVDE Preferred Language DG_5_3_887_Rel_Notes.pdf (binary) Release Notes MUNVDE Preferred Language DG_5_3_887_Implement_Guide.pdf (binary) Implementation Guide ADT Module/Registration DG_5_3_p887_reg_um.pdf (binary) Menu User Manual Patch Installation: Pre/Post Installation Overview ------------------------------ This multi-package build is distributed as a host file: PATIENT_PREFERRED_LANG.KID; this file can be obtained from one of the anonymous SFTP directories. File Name Contents Retrieval Format ---------------------------- -------- ---------------- PATIENT_PREFERRED_LANG.KID DG*5.3*887 ASCII SD*5.3*619 Use default answers for KIDS load/install questions. Multi-Build: http://code.osehra.org/VistA.git/blob/master/Packages/MultiBuilds/PATIENT_PREFERRED_LANG.KID Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Scheduling/Patches/SD_5.3_619

Patch Subject: My HealtheVet during Pre-Registration Description: ============ This patch addresses NSR # 20150314 - Increase Engagement in My HealtheVet - MHV. The Preregister a Patient [DGPRE PRE-REGISTER OPTION] option is enhanced to increase patient engagement in the My HealtheVet initiative. The Increase Engagement in My HealtheVet (MHV) software was born from the Veterans Administration (VA) Innovation Program. Prospective projects are scrutinized for benefit, funding, and development through this initiative. The My HealtheVet (MHV) web portal is a vastly under-utilized resource. As a result, patients are left with long wait times when trying to reach VHA to determine appointment date/times, refill prescriptions, or talk with a healthcare provider. All of these problems are easily mitigated with registration into the MHV web portal. There is currently no consistent process by which veterans are engaged about their desire to register in MHV or what their MHV status is. Pre-registration of patients is the one standardized process performed across VHA. To streamline the education of patients on MHV, VA requires a prompt in the VistA pre-registration screen indicating the Veterans' desire to participate in the MHV program, as well as their current MHV status. My HealtheVet Engagement/Registration Alert/Reminder ---------------------------------------------------- The Preregister a Patient [DGPRE PRE-REGISTER OPTION] option is enhanced to (1) display a message alerting the clerk that the selected patient has not completed My HealtheVet registration and (2) allows the patient's desire to be excluded from My HealtheVet to be documented. My HealtheVet Engagement Actions -------------------------------- The Preregister a Patient [DGPRE PRE-REGISTER OPTION] option has been enhanced to allow Pre-Registration clerks to capture a patient's My HealtheVet registration status and actions performed to assist with a patient's My HealtheVet registration. Disable/Enable My HealtheVet Registration Actions ----------------------------------------------- This functionality will automatically be turned off during the post install for this patch. When a site is ready to start using this functionality it can be enabled using the MAS Parameter Entry/Edit [DG PARAMETER ENTRY] option. After the functionality has been enabled, if for some reason a site determines they no longer want this functionality enabled, it can be disable using the same option. This can be done as follows: PIMS VERSION 5.3 PARAMETER ENTRY/EDIT ======================================================================= [1] Medical Center Name : ALBANY Affiliated: NO Multidivisional : YES Nursing Home Wards : NO Domiciliary Wards: YES System Timeout Sec. : 600 Print PTF Messages: NO Default PTF Printer : NONE SPECIFIED High Intensity: ON Consistency Checker : ON Abbreviated Inquiry: YES Auto PTF Messages : YES Show Status Screen: NO [2] Days to Update Medicaid : 5 Maintain G&L Corrections: 90-DAYS Disposition late : 4-HOURS Supplemental 10/10: NO Ask HINQ at Registration : YES DRUG PROFILE with 10/10: YES CHOICE OF DRUG PROFILE? : YES Default Drug Profile: ACTION HEALTH SUMMARY with 10/10 : YES Default Health Summary: OUTPATIE Ask EMBOSS at Registration : NO Use Nearest Printer: NO Reg. Template (LOCAL) : PLW MINI10 Use Temp Address: YES Default Code Sheet Printer : A100/10/6/UP Ask Device in Reg.: YES Days to Maintain Sens. Data: 90 Print Encounter Form: NO Default EF Printer : NONE SPECIFIED Restrict PATIENT access : NO Purple Heart Sort : Descending [Pre-Registration] Sort Method : P Background Job Function: PA Days Between Calls : 90 Days to Maintain Log Entries: 120 Days to Pull Appointments : 14 Run for Weekend: NO Enable My HealtheVet Prompts: NO [3] Divisions: TROY (501), ALBANY (500), CINCINNATI (539), ALB-PRRTP (500PA), ALBANY OPC (500A4), 13000 (13000), Enter 'D' to view DIVISIONS, 1-3 to EDIT, or RETURN to QUIT: 2 DAYS TO UPDATE MEDICAID: 5// DAYS TO MAINTAIN G&L CORR: 90// TIME FOR LATE DISPOSITION: 4// SUPPLEMENTAL 10/10: DO NOT PRINT WITH 10 10// USE HINQ INQUIRY?: YES// PRINT DRUG PROFILES WITH 10-10: YES// CHOICE OF DRUG PROFILE TYPE?: YES// DEFAULT TYPE OF DRUG PROFILE: ACTION// PRINT HEALTH SUMMARY?: YES// DEFAULT HEALTH SUMMARY: OUTPATIENT// EMBOSSERS ON-LINE: NO// USE CLOSEST PRINTER: NO// REGISTRATION TEMPLATE (LOCAL): PLW MINI10// USE TEMPORARY ADDRESS: YES// DEFAULT CODE SHEET PRINTER: A100/10/6/UP// ASK DEVICE IN REGISTRATION: YES// DAYS TO MAINTAIN SENSITIVITY: 90// PRINT ENCOUNTER FORM AT REG.: RESTRICT PATIENT RECORD ACCESS: PRE-REGISTRATION SORT: PATIENT NAME// DAYS BETWEEN CALLS: 90// BACKGROUND JOB FUNCTION: DELETE CALLED PATIENTS AND ADD NEW // DAYS TO MAINTAIN LOG: 120// DAYS TO PULL APPOINTMENT: 14// RUN FOR WEEKEND: NO// Select CLINIC EXCLUSION: Select ELIGIBILITY EXCLUSION: PURPLE HEART SORT: Enable My HealtheVet Prompts?: NO// YES <- -Enter "YES" Here to enable Patch Components: ----------------- Files & Fields Associated: New/ Modified/ File Name (Number) Field Name (Number) Deleted ------------------ ------------------- --------- PATIENT (#2) MHV SOCIALIZATION (#537026) New MHV REGISTERED (#537027) New MHV AUTHENTICATED (#537028) New MHV SECURE MESSAGING (#537029) New MHVREG UPDATE DATE/TIME (#537030) New MHVAUTH UPDATE DATE/TIME (#537031) New MHVSM UPDATE DATE/TIME (#537032) New MHV REGISTER DECLINED TEXT (#537033) New MHV AUTH DECLINED TEXT (#537034) New MHV MSG DECLINED TEXT (#537035) New MHV REGISTER DECLINED REASON (#537036) New MHV AUTH DECLINED REASON (#537037) New MHV MSG DECLINED REASON (#537038) New MHV MSG ACTIONS (#537041) New MHV AUTH ACTIONS (#537042) New PATIENT (#2) Multiple (Sub-File) MHV SOCIALIZATION (#537026) New SOCIALIZATION DATE (#.01) New SOCIALIZATION RESPONSE (#1) New SOCIALIZATION ACTIONS (#2) New MHV SOCIALIZATION (#390.01) New NAME (#.01) New DISPLAY SEQUENCE (#1) New PATIENT TEXT (#2) New DISPLAY TEXT (#1.5) New FOLLOWUP ACTION (#3) New MHV SOCIALIZATION ACTIONS (#390.02) New ACTION (#.01) New SELECTABLE LOCATIONS (#1) New DISPLAY TEXT (#3) New MHV DECLINED REASONS (#390.03) New NAME (#.01) New SELECTABLE AT (#1) New MHV ACTION SELECTION (#390.04) New NAME (#.01) New DESCRIPTION (#1) New MAS PARAMETERS (#43) Enable My HealtheVet Prompts? (#1100.07) NEW Forms Associated: N/A Mail Groups Associated: N/A Options Associated: N/A Protocols Associated: N/A Security Keys Associated: N/A Templates Associated: N/A Additional Information: New Service Requests (NSRs): ---------------------------- 20150314 - Increase Engagement in My HealtheVet (MHV) Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- N/A Test Sites: ---------- VA Puget Sound Health Care System Cincinnati, OH Software and Documentation Retrieval Instructions: ---------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ Title File Name FTP Mode ----------------------------------------------------------------------- User Manual - Registration Menu dg_5_3_p903_reg_um.pdf binary PIMS Technical Manual pimstm.pdf binary Release Notes dg_5_3_p903_rn.pdf binary Patch Installation: Pre/Post Installation Overview: ------------------------------- This patch includes a post installation routine which does the following: 1. Files new 315 INCONSISTENT DATA ELEMENTS (#38.6) file entry for missing MHV registration status. This check ensures a patient has been asked about their registration, or interest in registering, in My HealtheVet. 2. Disables this functionality for all sites by setting the "Enable My HealtheVet Prompts?" (#1100.07) field in the MAS PARAMETER (#43) file to "NO". The DG903PST post installation routine will be automatically deleted as part of the installation process. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Registration/Patches/DG_5.3_903

Patch Subject: FEE SEPARATION OF DUTIES ENHANCEMENT Description: ============ ************************************************************************ * If your site is using the Fee Basis Claims System (FBCS), you must * * install DSIF*3.2*38 immediately after installing FB*3.5*154 to * * avoid application/processing errors. If your site is not using * * FBCS, there is no need to install the FBCS patch. * ************************************************************************ ************************************************************************ * Before installing patch FB*3.5*154 identify user accounts that must * * be allocated new security keys per the post install step to * * minimize disruption of business processes. * ************************************************************************ This patch is dedicated to the memory of Mr. Les Niemiec, VHA National Fee Program Manager from 2005-2009. He always went the extra mile for Veterans, and was a major force in developing and managing the Fee programs that serve our Veterans and their families. Patch FB*3.5*154 is one of the Fee Basis patches for the VistA Fee Separation of Duties project. Patches FB*3.5*151, FB*3.5*165, and FB*3.5*172 are other Fee Basis patches generated by the project. Patch FB*3.5*154 revises the locks on existing functionality and menu options to enhance the separation of duty controls. This patch also modifies the software to enforce separation of duty business rules. This patch resolves an existing problem with the identification of the associated authorization for outpatient payments and inpatient ancillary payments. This patch modifies the software to prevent an undefined error when a prescription is deleted. This patch modifies the software to prevent an undefined error when rejected payments are re-initiated. Detailed descriptions of the enhancements follow: 01. SECURITY KEYS This patch adds three new security keys, if they don't already exist, and modifies the description of the existing FBAASUPERVISOR security key. The new keys give sites more control of user's access to the package functions. Additionally, this patch modifies the software to lock many functions with the FBAA LEVEL 2 key instead of the FBAASUPERVISOR key. This is expected to reduce the number of individuals who need to hold the FBAASUPERVISOR key. Lead clerks and supervisors may be assigned more than one of these keys. The four keys exported by the patch are listed below: Key: FBAA LEVEL 1 AUTH Permits the holder to enter and edit 7079 authorizations, 7078 authorizations, civil hospital notifications, nursing home movements, and unauthorized claims. Key: FBAA LEVEL 1 PMT Permits the holder to enter and edit invoices and payments. Key: FBAA LEVEL 2 Permits the holder to certify a batch for payment, queue data for transmission to Central FEE, void payments, and update contract and rate data for nursing home vendors. The holder of this key can also bypass some user and status restrictions during selection of a payment or batch. This key is normally assigned to a lead clerk or supervisor. Key: FBAASUPERVISOR Permits the holder to edit site parameters, maintain the VA fee schedule, edit the contract file, reprocess an overdue batch, resend a completed batch, re-transmit MRAs, and purge MRAs. This key is normally assigned to a supervisor. 02. REVISE LOCKS ON MENU OPTIONS Menu options can be locked by a security key. A locked option can only be accessed by users who hold the applicable security key. This patch modifies locks on the menu options. Menu options used to modify authorizations are generally locked by the new FBAA LEVEL 1 AUTH security key. Menu options used to process payments are generally locked by the new FBAA LEVEL 1 PMT security key. Menu options normally restricted to a lead clerk or supervisor are locked by the new FBAA LEVEL 2 security key. Menu options normally restricted to a supervisor are locked by the FBAASUPERVISOR security key. A list of menu options (sorted by menu) whose lock is modified by the patch follows: The old lock column shows the lock in place (if any) prior to installation of the patch. Menu Option Lock Old Lock --------------------------------- ----------------- -------------- Civil Hospital Main Menu Queue Data for Transmission FBAA LEVEL 2 FBAASUPERVISOR Notification/Request Menu Legal Entitlement FBAA LEVEL 1 AUTH Medical Entitlement FBAA LEVEL 1 AUTH Delete Notification/Request FBAA LEVEL 1 AUTH Reconsider a Denied Request FBAA LEVEL 2 FBAASUPERVISOR Disposition Menu Complete 7078/Authorization FBAA LEVEL 1 AUTH Edit Completed 7078 FBAA LEVEL 1 AUTH Cancel 7078 Entered in Error FBAA LEVEL 2 FBAASUPERVISOR Print List of Cancelled 7078 FBAA LEVEL 2 FBAASUPERVISOR Set-up a 7078 FBAA LEVEL 1 AUTH Payment Process Menu Ancillary Contract Hosp/CNH Payment FBAA LEVEL 1 PMT Complete a Payment FBAA LEVEL 1 PMT Delete Inpatient Invoice FBAA LEVEL 1 PMT Edit Ancillary Payment FBAA LEVEL 1 PMT Enter Invoice/Payment FBAA LEVEL 1 PMT Invoice Edit FBAA LEVEL 1 PMT Multiple Ancillary Payments FBAA LEVEL 1 PMT Patient Reimbursement for Ancillary Services FBAA LEVEL 1 PMT Reimbursement for Inpatient Hospital Invoice FBAA LEVEL 1 PMT Batch Main Menu - CH Open a Batch FBAA LEVEL 1 PMT Edit Batch data FBAA LEVEL 1 PMT Close-out Batch FBAA LEVEL 1 PMT Re-open Batch FBAA LEVEL 1 PMT Pricer Batch Release FBAA LEVEL 1 PMT Re-initiate Pricer Rejected Items FBAA LEVEL 1 PMT Release a Batch FBAA LEVEL 2 FBAASUPERVISOR Re-initiate Rejected Payment Items FBAA LEVEL 1 PMT Batch Delete FBAA LEVEL 1 PMT Open Ancillary Payment Batch FBAA LEVEL 1 PMT Community Nursing Home Main Menu Queue Data for Transmission FBAA LEVEL 2 FBAASUPERVISOR Update Vendor Contract/Rates - CNH FBAA LEVEL 2 Authorization Main Menu - CNH Enter CNH Authorization FBAA LEVEL 1 AUTH Edit CNH Authorization FBAA LEVEL 1 AUTH Cancel Authorization Entered in Error FBAA LEVEL 2 FBAASUPERVISOR Change Existing Contract Rate for a Patient FBAA LEVEL 1 AUTH Delete CNH Rate FBAA LEVEL 2 Enter Veteran Rates under new Vendor Contract FBAA LEVEL 1 AUTH Print List of Cancelled 7078 FBAA LEVEL 2 FBAASUPERVISOR Batch Main Menu - CNH Batch Delete FBAA LEVEL 1 PMT Close-out Batch FBAA LEVEL 1 PMT Edit Batch data FBAA LEVEL 1 PMT Open CNH Batch FBAA LEVEL 1 PMT Re-initiate Rejected Payment Items FBAA LEVEL 1 PMT Re-open Batch FBAA LEVEL 1 PMT Release a Batch FBAA LEVEL 2 FBAASUPERVISOR Fee Fund Control Main Menu - CNH Estimate Funds for Obligation FBAA LEVEL 1 AUTH Post Commitments for Obligation FBAA LEVEL 1 AUTH Movement Main Menu - CNH Admit To CNH FBAA LEVEL 1 AUTH Delete Movement Menu FBAA LEVEL 1 AUTH Discharge From CNH FBAA LEVEL 1 AUTH Edit Movement Menu FBAA LEVEL 1 AUTH Transfer Movement FBAA LEVEL 1 AUTH Delete Movement Menu Admission Delete FBAA LEVEL 1 AUTH Discharge Delete FBAA LEVEL 1 AUTH Transfer Delete FBAA LEVEL 1 AUTH Edit Movement Menu Admission Edit FBAA LEVEL 1 AUTH Discharge Edit FBAA LEVEL 1 AUTH Transfer Edit FBAA LEVEL 1 AUTH Payment Main Menu - CNH Delete Inpatient Invoice FBAA LEVEL 1 PMT Edit CNH Payment FBAA LEVEL 1 PMT Enter CNH Payment FBAA LEVEL 1 PMT Medical Fee Main Menu Enter Authorization FBAA LEVEL 1 AUTH Supervisor Main Menu FBAA LEVEL 2 FBAASUPERVISOR Terminate ID Card FBAA LEVEL 1 AUTH Batch Main Menu Batch Delete FBAA LEVEL 1 PMT Close-out Batch FBAA LEVEL 1 PMT Edit Batch data FBAA LEVEL 1 PMT Open a Batch FBAA LEVEL 1 PMT Re-open Batch FBAA LEVEL 1 PMT Release a Batch FBAA LEVEL 2 FBAASUPERVISOR Outputs Main Menu Group 7079 Print FBAA LEVEL 2 FBAASUPERVISOR Payment menu Delete Payment Entry FBAA LEVEL 1 PMT Edit Payment FBAA LEVEL 1 PMT Enter Payment FBAA LEVEL 1 PMT Multiple Payment Entry FBAA LEVEL 1 PMT Re-initiate Rejected Payment Items FBAA LEVEL 1 PMT Reimbursement Payment Entry FBAA LEVEL 1 PMT Travel Payment Only FBAA LEVEL 1 PMT Supervisor Main Menu Clerk Look-Up For An Authorization FBAASUPERVISOR FBAASUPERVISOR by FBAACLU Enter/Edit Suspension Letters FBAASUPERVISOR Edit Pharmacy Invoice Status FBAA LEVEL 2 Fee Basis 1358 Segregation of Duty Report FBAASUPERVSIOR Pricer Batch Release FBAA LEVEL 1 PMT Queue Data for Transmission FBAA LEVEL 2 FBAASUPERVISOR Re-initiate Rejected Payment Items FBAA LEVEL 1 PMT Release a Batch FBAA LEVEL 2 FBAASUPERVISOR Void Payment Main Menu FBAA LEVEL 2 Fee Schedule Main Menu (under Supervisor Main Menu) Add/Edit Fee Schedule FBAASUPERVISOR Compile Fee Schedule FBAASUPERVISOR FPPS Update & Transmit Menu (under Supervisor Main Menu) Outpatient/Ancillary Invoice Edit FBAA LEVEL 2 FBAASUPERVISOR Pharmacy Invoice Edit FBAA LEVEL 2 FBAASUPERVISOR Inpatient Invoice Edit FBAA LEVEL 2 FBAASUPERVISOR Purge Message Text FBAA LEVEL 2 FBAASUPERVISOR MRA Main Menu (under Supervisor Main Menu) Vendor MRA Main Menu FBAA LEVEL 2 FBAASUPERVISOR Veteran MRA Main Menu FBAA LEVEL 2 Vendor MRA Main Menu (under MRA Main Menu) Update FMS Vendor File in Austin FBAA LEVEL 2 FBAASUPERVISOR Delete Vendor MRA FBAA LEVEL 2 FBAASUPERVISOR Reinstate Vendor MRA FBAA LEVEL 2 MRA'S Awaiting Austin Approval FBAA LEVEL 2 Veteran MRA Main Menu (under MRA Main Menu) Add type Veteran MRA FBAA LEVEL 2 Change type Veteran MRA FBAA LEVEL 2 Delete type Veteran MRA FBAA LEVEL 2 Reinstate type Veteran MRA FBAA LEVEL 2 Unauthorized Claims File Menu (under Supervisor Main Menu) Add New Person for Unauthorized Claim FBAA LEVEL 1 AUTH Disapproval Reasons File Enter/Edit FBAASUPERVISOR Dispositions File Edit FBAASUPERVISOR Request Info File Enter/Edit FBAASUPERVISOR Void Payment Main Menu (under Supervisor Main Menu) CH Delete Void Payment FBAA LEVEL 2 FBAASUPERVISOR by FBCHVP CH Void Payment FBAA LEVEL 2 FBAASUPERVISOR by FBCHVP CNH Delete Void Payment FBAA LEVEL 2 FBAASUPERVISOR by FBCHVP CNH Void Payment FBAA LEVEL 2 FBAASUPERVISOR by FBCHVP Medical Delete Void Payment FBAA LEVEL 2 FBAASUPERVISOR by FBAAVP Medical Void Payment FBAA LEVEL 2 FBAASUPERVISOR by FBAAVP Pharmacy Delete Void Payment FBAA LEVEL 2 FBAASUPERVISOR by FBAAPHV Pharmacy Void Payment FBAA LEVEL 2 FBAASUPERVISOR by FBAAPHV Pharmacy Fee Main Menu Closeout Pharmacy Invoice FBAA LEVEL 1 PMT Complete Pharmacy Invoice FBAA LEVEL 1 PMT Edit Pharmacy Invoice FBAA LEVEL 1 PMT Enter Pharmacy Invoice FBAA LEVEL 1 PMT Patient Re-imbursement FBAA LEVEL 1 PMT Batch Menu - Pharmacy Batch Delete FBAA LEVEL 1 PMT Close-out Batch FBAA LEVEL 1 PMT Edit Batch data FBAA LEVEL 1 PMT Open a Pharmacy Batch FBAA LEVEL 1 PMT Re-open Batch FBAA LEVEL 1 PMT Release a Batch FBAA LEVEL 2 FBAASUPERVISOR State Home Main Menu Enter New State Home Authorization FBAA LEVEL 1 AUTH Change a State Home Authorization FBAA LEVEL 1 AUTH Delete a State Home Authorization FBAA LEVEL 1 AUTH Reinstate State Home Authorization FBAA LEVEL 1 AUTH Unauthorized Claim Main Menu Request Information on Unauthorized Claim FBAA LEVEL 1 AUTH Receive Requested Information FBAA LEVEL 1 AUTH Letters for Unauthorized Claim FBAA LEVEL 1 AUTH Payments for Unauthorized Claims FBAA LEVEL 1 PMT Enter/Edit Unauthorized Claim Menu Enter Unauthorized Claim FBAA LEVEL 1 AUTH Modify Unauthorized Claim FBAA LEVEL 1 AUTH Disposition Unauthorized Claim FBAA LEVEL 1 AUTH Re-open Unauthorized Claim FBAA LEVEL 1 AUTH Initiate Appeal for Unauthorized Claim FBAA LEVEL 1 AUTH Appeal Edit for Unauthorized Claim FBAA LEVEL 2 COVA Appeal Enter/Edit FBAA LEVEL 2 Letters for Unauthorized Claim Update Date Letter Sent FBAA LEVEL 1 AUTH Batch Print Letters FBAA LEVEL 1 AUTH Reprint Letter(s) FBAA LEVEL 1 AUTH Utilities for Unauthorized Claims Add New Person for Unauthorized Claim FBAA LEVEL 1 AUTH Associate an Unauthorized Claim to a Primary FBAA LEVEL 1 AUTH Disassociate an Unauthorized Claim FBAA LEVEL 1 AUTH Return Address Display/Edit FBAA LEVEL 2 03. ATTACH MENU OPTIONS TO ADDITIONAL MENUS Several menu options that are attached to the Supervisor Main Menu are now also attached to additional menus so they can be utilized by users who should not have access to the supervisor menu. Delete reject flag Added to Batch Main Menu (under Medical Fee Main Menu) Added to Batch Menu - Pharmacy (under Pharmacy Fee Main Menu) Finalize a Batch Added to Batch Main Menu (under Medical Fee Main Menu) Added to Batch Menu - Pharmacy (under Pharmacy Fee Main Menu) List Batches Pending Release Added to Batch Main Menu (under Medical Fee Main Menu) Added to Batch Menu - Pharmacy (under Pharmacy Fee Main Menu) Added to Batch Main Menu - CH (under Civil Hospital Main Menu) 04. REVISE LOCKS DURING SELECTION OF PAYMENTS Many options used to enter or edit payments and payment batches prevent selection of a payment or batch that was entered by another user. This restriction is not imposed on a user who holds the FBAASUPERVISOR security key. Many options used to enter or edit payments and payment batches prevent selection of a payment or batch when the batch has certain status values such as supervisor closed. Fewer batch status values are restricted for a user who holds the FBAASUPERVISOR security key. The following menu options are modified by this patch to check for the new FBAA LEVEL 2 security key INSTEAD OF the existing FBAASUPERVISOR security key when imposing restrictions on the selection of a payment or payment batch. Edit Batch data [FBAA BATCH EDIT] Close-out Batch [FBAA CLOSE BATCH] Re-open Batch [FBAA REOPEN BATCH] Batch Delete [FBAA BATCH DELETE] Enter Payment [FBAA ENTER PAYMENT] Multiple Payment Entry [FBAA MULTIPLE PAYMENT ENTRY] Reimbursement Payment Entry [FBAA MEDICAL REIMBURSEMENT] Ancillary Contract Hosp/CNH Payment [FBCH ANCILLARY PAYMENT] Multiple Ancillary Payments [FBCH MULTIPLE PAYMENTS] Patient Reimbursement for Ancillary Services [FBCH ANCILLARY REIMBURSEMENT] Payments for Unauthorized Claims [FBUC PAYMENTS] Delete Payment Entry [FBAA DELETE PAYMENT] Complete a Payment [FBCH COMPLETE PAYMENT] Re-initiate Pricer Rejected Items [FBCH REINITIATE PRICER REJECTS] Delete Inpatient Invoice [FBCH DELETE INVOICE] Invoice Edit [FBCH EDIT PAYMENT] Edit CNH Payment [FBCNH EDIT PAYMENT] Delete Inpatient Invoice [FBCH DELETE INVOICE] Edit Payment [FBAA EDIT PAYMENT] Edit Ancillary Payment [FBCH EDIT ANCILLARY PAYMENT] Edit Pharmacy Invoice [FBAA EDIT PHARMACY INVOICE] 05. REVISE LOCKS DURING SELECTION OF CIVIL HOSPITAL NOTIFICATIONS The option Delete Notification/Request [FBCH DELETE REQUEST] currently restricts the selection of a notification/request to the USER ENTERING NOTIFICATION unless the FBAASUPERVISOR key is held. This option is modified by this patch to instead check if the user holds the FBAA LEVEL 2 security key. 06. REMOVE LOCK ON ENTRY OF AN AMOUNT PAID THAT EXCEEDS THE AMOUNT CLAIMED Menu options used to enter or edit outpatient and ancillary inpatient payments do not allow the user to enter an amount paid that exceeds the amount claimed or exceeds the calculated fee schedule amount unless the user holds the FBAASUPERVISOR key. This patch modifies the software by removing the requirement that a user hold the FBAASUPERVISOR security key to enter an amount paid that exceeds the amount claimed or fee schedule amount. The following options are modified: Enter Payment [FBAA ENTER PAYMENT] Multiple Payment Entry [FBAA MULTIPLE PAYMENT ENTRY] Reimbursement Payment Entry [FBAA MEDICAL REIMBURSEMENT] Ancillary Contract Hosp/CNH Payment [FBCH ANCILLARY PAYMENT] Multiple Ancillary Payments [FBCH MULTIPLE PAYMENTS] Patient Reimbursement for Ancillary Services [FBCH ANCILLARY REIMBURSEMENT] Payments for Unauthorized Claims [FBUC PAYMENTS] Edit Payment [FBAA EDIT PAYMENT] Edit Ancillary Payment [FBCH EDIT ANCILLARY PAYMENT] 07. ADD LOCK TO THE UPDATE OF CNH CONTRACT OR RATE DATA This patch locks with the FBAA LEVEL 2 security key the ability to update contract and rate data for a community nursing home vendor. The following options are modified to check if user holds the security key before allowing the contract and rate data to be updated: Vendor Enter/Edit [FBCNH VENDOR ENTER/EDIT] Display,Enter,Edit Demographics [FBAA VENDOR DEMOGRAPHICS] 08. ADD LOCK TO AN INTERACTIVE FPPS TRANSMIT DATA The Transmit Invoices to FPPS [FB FPPS TRANSMIT] option is modified by this patch to require the user to hold the FBAA LEVEL 2 security key when the option is run interactively from the menu. The patch does not make any changes to the option when it is run as a scheduled task (non-interactively). 09. LIST OF PENDING 7078S MODIFIED TO CONSIDER DIFFERENT SECURITY KEY The following menu option only shows pending 7078s entered by the user unless the FBAASUPERVISOR key is held: This option is changed to check if the user holds the FBAA LEVEL 2 security key rather than the FBAASUPERVISOR security key. Civil Hospital Main Menu [FBCH MAIN MENU] 10. CREATE USER ACCESS REPORT This patch creates a new option called Security Key Report for Fee Basis [FB SEC KEY RPT]. This option is attached to the Supervisor Main Menu [FBAA SUPERVISOR OPTIONS] and it is locked by the FBAASUPERVISOR security key. The new option generates a report of users that hold Fee Basis security keys. An example is shown below: Select Supervisor Main Menu <TEST ACCOUNT> Option: SECurity Key Report for Fee Basis Should report include terminated users with keys? NO// Sort by Security Key or User: (S/U): SECURITY KEY Select Fee Basis Security Key: ALL// DEVICE: HOME// Security Key Report for Fee Basis OCT 17, 2014@11:01:28 page 1 by Security Key for all FB keys Name SSN Title ----------------------------------- ---- ----------------------------- Key: FB ARCH FEEUSER,FIRST 2709 COMPUTER SYSTEMS ANALYST Division(s): 500, 688 FEEUSER,SECOND 8420 Division(s): 500 Key: FBAA LEVEL 1 AUTH FEEUSER,FIRST 2709 COMPUTER SYSTEMS ANALYST Division(s): 500, 688 FEEUSER,THIRD 1234 COMPUTER SYSTEMS ANALYST Division(s): 500, 688 11. DISABLE SITE PARAMETER EDIT AUTH. DURING PAYMENT The site parameter EDIT AUTH. DURING PAYMENT allows selected authorization fields to be edited when some types of payments are entered. This site parameter is disabled by this patch and will no longer be asked when the site parameters are edited or have any effect on the software behavior. 12. PREVENT ENTRY OF PAYMENT OR PRICING IF USER ENTERED AUTHORIZATION This patch modifies the software to prevent a user from entering payment or pricing for a service if that user previously entered or edited the associated authorization for the service. Entry or edit of a civil hospital notification, community nursing home contract rate for a patient, community nursing home movement, or unauthorized claim is considered as a change to the associated authorization. The options used to enter or edit 'authorizations' are modified to keep track of users. The options used to process payments are modified to prevent the user who entered or edited the 'authorization' associated with the payment from proceeding. 13. NURSING HOME DAILY RATE CANNOT BE ENTERED DURING PAYMENT This patch modifies the Enter CNH Payment [FBCNH ENTER PAYMENT] option to no longer allow entry of missing daily rates. An update to the daily rate is considered an edit of the authorization and the person who processes the payment cannot edit the authorization per separation of duties. 14. DISPLAY USERS THAT ENTERED OR EDITED RECORDS This patch modifies the Clerk Look-Up For An Authorization report and adds three new reports to display the list of users who entered or edited an authorization or associated records. These options are locked by the FBAASUPERVISOR security key. Clerk Look-Up For An Authorization [FBAA CLERK LOOK-UP] This option will list users that entered or edited a specified authorization in the FEE BASIS PATIENT file. When applicable the output will also show users that entered or edited the civil hospital notification or unauthorized claims associated with the authorization. Clerk Lookup for 7078 Authorization [FBCH CLERK LOOKUP] This option will list users that entered or edited a specified 7078 authorization. Entry or edit of nursing home rate and movements are included in this output. When applicable the output will also show users that entered or edited the civil hospital notification associated with the authorization. Clerk Lookup for Notification/Request [FBCH REQUEST CLERK LOOKUP] This option will list users that entered or edited a specified notification/request. Clerk Lookup for Unauthorized Claim [FBUC CLERK LOOKUP] This option will list users that entered or edited a specified unauthorized claim. 15. PAYMENT REFERENCE TO AUTHORIZATION ISSUE There can be a problem with the association of an outpatient or inpatient ancillary payment to the appropriate authorization. The problem occurs when there are payments that should be associated with different authorizations, but those payments have the exact same patient, vendor, and date of service. This situation is common with home health services where there are separate authorizations for nursing and non-nursing services for a single patient and those services are provided to the patient by the same vendor on the same date. This problem can result in various errors including sending the wrong purpose of visit code when a payment batch is sent to Central FEE. The problem was originally reported on Remedy Ticket 726099. A fix for this issue was requested by new service request 20120609. This patch modifies the software to prevent the problem from occurring for new payments. Additionally, when the patch is installed a one-time job will examine existing payments and correct many or all of the existing inappropriate associations. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- FEE BASIS PATIENT (#161) AUTHORIZATION (#161.01) USER AUDIT (#292) New FEE BASIS SITE *EDIT AUTH. DURING Modified PARAMETERS (#161.4) PAYMENT (#19) FEE BASIS PAYMENT (#162) INITIAL TREATMENT DATE *AUTHORIZATION Modified (#162.02) POINTER (#3) SERVICE PROVIDED AUTHORIZATION New (#162.03) POINTER (#15.5) AMOUNT PAID (#2) Modified TRAVEL PAYMENT DATE AUTHORIZATION New (#162.04) POINTER (#15) FEE NOTIFICATION/REQUEST USER AUDIT (#292) New (#162.2) VA FORM 10-7078 (#162.4) USER AUDIT (#292) New FEE BASIS UNAUTHORIZED USER AUDIT (#292) New CLAIMS (#162.7) Forms Associated: N/A Mail Groups Associated: N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- FB FPPS PURGE run routine Modified FB SEC KEY RPT run routine New FB SEG DUTY RPT run routine Modified FBAA BATCH DELETE run routine Modified FBAA BATCH EDIT run routine Modified FBAA BATCH MENU menu USE AS LINK FBAA CALCULATE SCHEDULE run routine Modified FBAA CANCEL MEDICAL VOID run routine Modified FBAA CANCEL PHARMACY VOID run routine Modified FBAA CLERK LOOK-UP run routine Modified FBAA CLOSE BATCH run routine Modified FBAA CLOSE OUT INVOICE run routine Modified FBAA COMPLETE PHARMACY INVOICE run routine Modified FBAA DELETE PAYMENT run routine Modified FBAA EDIT INVOICE STATUS edit Modified FBAA EDIT PAYMENT run routine Modified FBAA EDIT PHARMACY INVOICE run routine Modified FBAA EDIT SCHEDULE run routine Modified FBAA ENTER AUTHORIZATION run routine Modified FBAA ENTER PAYMENT run routine Modified FBAA ENTER PHARMACY INVOICE run routine Modified FBAA ENTER/EDIT LETTERS run routine Modified FBAA FINALIZE BATCH run routine ATTACH TO MENU FBAA FMS UPDATE run routine Modified FBAA FPPS EDIT INVOICE run routine Modified FBAA LIST CLOSED BATCHES run routine ATTACH TO MENU FBAA MEDICAL REIMBURSEMENT run routine Modified FBAA MEDICAL VOID PAYMENT run routine Modified FBAA MRA DELETE VENDOR run routine Modified FBAA MRA VENDOR REINSTATE run routine Modified FBAA MRA VETERAN ADD TYPE action Modified FBAA MRA VETERAN CHANGE TYPE action Modified FBAA MRA VETERAN DELETE TYPE action Modified FBAA MRA VETERAN REINSTATE action Modified FBAA MRA'S AWAITING APPROVAL run routine Modified FBAA MULTIPLE PAYMENT ENTRY run routine Modified FBAA OPEN BATCH run routine Modified FBAA OPEN PHARMACY BATCH action Modified FBAA PHARMACY BATCH OPTIONS menu USE AS LINK FBAA PHARMACY VOID PAYMENT run routine Modified FBAA PRINT 7079 GROUP run routine Modified FBAA QUEUE DATA FOR TRANS. run routine Modified FBAA REIMBURSEMENT PHARMACY action Modified FBAA REINITIATE REJECTS run routine Modified FBAA REOPEN BATCH run routine Modified FBAA SUPERVISOR OPTIONS menu MERGE MENU ITEMS FBAA SUPERVISOR RELEASE run routine Modified FBAA TERMINATE ID CARD run routine Modified FBAA TRAVEL ENTRY run routine Modified FBAA VENDOR MRA MAIN MENU menu Modified FBAA VETERAN MRA MAIN MENU menu Modified FBAA VOID PAYMENT MENU menu Modified FBAA VOUCHER DELETE REJECT run routine ATTACH TO MENU FBCH 7078 SETUP run routine Modified FBCH ANCILLARY PAYMENT run routine Modified FBCH ANCILLARY REIMBURSEMENT run routine Modified FBCH BATCH OPTIONS menu USE AS LINK FBCH CANCEL 7078 run routine Modified FBCH CLERK LOOKUP run routine New FBCH COMPLETE 7078 run routine Modified FBCH COMPLETE PAYMENT run routine Modified FBCH DELETE INVOICE run routine Modified FBCH DELETE REQUEST run routine Modified FBCH DELETE VOID run routine Modified FBCH EDIT 7078 run routine Modified FBCH EDIT ANCILLARY PAYMENT run routine Modified FBCH EDIT PAYMENT run routine Modified FBCH ENTER PAYMENT run routine Modified FBCH FPPS EDIT INVOICE run routine Modified FBCH LEGAL ENTITLEMENT run routine Modified FBCH MEDICAL ENTITLEMENT run routine Modified FBCH MULTIPLE PAYMENTS run routine Modified FBCH NOTIFICATION MENU menu USE AS LINK FBCH OPEN ANCILLARY BATCH run routine Modified FBCH OPEN BATCH run routine Modified FBCH OUTPUT MENU menu USE AS LINK FBCH PRICER RELEASE run routine Modified FBCH PRINT CANCELLED 7078 print Modified FBCH REIMBURSEMENT INVOICE run routine Modified FBCH REINITIATE PRICER REJECTS run routine Modified FBCH REOPEN REQUEST run routine Modified FBCH REQUEST CLERK LOOKUP run routine New FBCH VOID PAYMENT run routine Modified FBCNH ADMIT run routine Modified FBCNH CANCEL 7078 run routine Modified FBCNH DELETE ADMISSION run routine Modified FBCNH DELETE DISCHARGE run routine Modified FBCNH DELETE MOVEMENT MENU menu Modified FBCNH DELETE RATE run routine Modified FBCNH DELETE TRANSFER run routine Modified FBCNH DELETE VOID run routine Modified FBCNH DISCHARGE run routine Modified FBCNH EDIT ADMISSION run routine Modified FBCNH EDIT AUTHORIZATION run routine Modified FBCNH EDIT DISCHARGE run routine Modified FBCNH EDIT MOVEMENT menu Modified FBCNH EDIT PAYMENT action Modified FBCNH EDIT TRANSFER run routine Modified FBCNH ENTER AUTHORIZATION run routine Modified FBCNH ENTER PAYMENT run routine Modified FBCNH ENTER VETERAN RATES run routine Modified FBCNH ESTIMATE FUNDS action Modified FBCNH OPEN BATCH action Modified FBCNH OUTPUTS MAIN MENU menu USE AS LINK FBCNH POST COMMITMENTS run routine Modified FBCNH RATE CHANGE run routine Modified FBCNH TRANSFER run routine Modified FBCNH UPDATE VENDOR CONTRACT run routine Modified FBCNH VOID PAYMENT run routine Modified FBRX FPPS EDIT INVOICE run routine Modified FBSH CHANGE AUTH run routine Modified FBSH DELETE AUTH run routine Modified FBSH ENTER AUTH run routine Modified FBSH REINSTATE AUTH run routine Modified FBUC ADD NEW PERSON run routine Modified FBUC APPEAL EDIT run routine Modified FBUC ASSOCIATE run routine Modified FBUC BATCH PRINT LETTERS run routine Modified FBUC CLERK LOOKUP run routine New FBUC COVA APPEAL run routine Modified FBUC DISAPPROVAL REASONS FILE run routine Modified FBUC DISASSOCIATE run routine Modified FBUC DISPOSITION UNAUTH CLAIM run routine Modified FBUC DISPOSITIONS FILE run routine Modified FBUC ENTER run routine Modified FBUC INITIATE APPEAL run routine Modified FBUC LETTERS menu Modified FBUC MODIFY UNAUTHORIZED CLAIM run routine Modified FBUC OUTPUTS menu USE AS LINK FBUC PAYMENTS run routine Modified FBUC RECEIVE INFORMATION run routine Modified FBUC REOPEN run routine Modified FBUC REPRINT LETTER(S) run routine Modified FBUC REQUEST INFO FILE run routine Modified FBUC REQUEST INFORMATION run routine Modified FBUC RETURN ADDRESS DIS/ED run routine Modified FBUC UPDATE DATE LETTER SENT run routine Modified Protocols Associated: N/A Security Keys Associated: Security Key Name New/Modified/Deleted ----------------- -------------------- FBAA LEVEL 1 AUTH New FBAA LEVEL 1 PMT New FBAA LEVEL 2 New FBAASUPERVISOR Modified Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- FBAA SITE PARAMETERS Input FEE BASIS SITE Modified PARAMETERS (#161.4) Additional Information: N/A New Service Requests (NSRs): ---------------------------- 20090309 Emergency Patch VistA Fee - Separation of Duties - Assignment of Keys 20120609 PROBLEM WITH FEE BASIS PAYMENT FILE/POV ISSUE Patient Safety Issues (PSIs): ----------------------------- N/A Remedy Ticket(s) & Overview: ---------------------------- 1. REMEDY Ticket 833468 Problem: An undefined error occurs when a prescription is deleted from an existing pharmacy invoice using the Edit Pharmacy Invoice [Edit Pharmacy Invoice] option. Resolution: This patch modifies routine FBAAEPI to prevent the undefined error from occurring. 2. REMEDY Ticket 985307 Problem: The Re-initiate Rejected Payment Items [FBAA REINITIATE REJECTS] option contains a fault when it is used to re-initiate all items in an outpatient or ancillary inpatient (type B3) payment batch. The problem does not occur when the line items are individually re-initiated. The software attempts to track all payment lines (sorted by invoice) that are re-initiated into the new batch. If all the lines on an invoice are not moved into the new batch the re-initiated lines are assigned a different invoice number so an invoice is not spilt between two different payment batches. The problem is that the software does not determine the invoice number when a line is re-initiated. If the batch was previously displayed the invoice of the last displayed line item is inappropriately treated as the invoice of all the re-initiated line items. If the batch was not displayed the option abends with an undefined error for variable FBIN. Resolution: The problem is corrected by modifying routine FBAARR1 within line tag REJM so the invoice number of a line item is appropriately determined before it is referenced later in that section of code. Test Sites: ----------- CENTRAL PLAINS HCS TUCSON, AZ Documentation Retrieval Instructions: ------------------------------------- Updated documentation describing the new functionality introduced by this patch is available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ Title File Name SFTP Mode ----------------------------------------------------------------------- Fee Basis User Manual FEE3_5_UM_R1016.PDF (binary) Fee Basis Technical Manual FEE3_5_TM_R1016.PDF (binary) Release Notes FB*3.5*154 FEE3_5_P154_RN.PDF (binary) Patch Installation: Pre/Post Installation Overview: ------------------------------- Before installing the patch, the FBAA LEVEL 1 AUTH, FBAA LEVEL 1 PMT, and FBAA LEVEL 2 security keys must be allocated to appropriate users. The patch contains a post install routine that automatically populates new fields for existing records. The post install routine creates entries in the new USER AUDIT multiple of the following files based on existing data: FEE BASIS PATIENT (#161) FEE NOTIFICATION/REQUEST (#162.2) VA FORM 10-7078 (#162.4) FEE BASIS UNAUTHORIZED CLAIM (#162.7) The post install populates the new AUTHORIZATION POINTER field in the SERVICE PROVIDED multiple of the FEE BASIS PAYMENT (#162) file based on existing data. After the patch is installed the FBAASUPERVISOR security key must be de-allocated from user accounts that no longer require that key. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Fee+Basis/Patches/FB_3.5_154

Patch Subject: CORRECT ADT AND ARS INDEXES FOR PATIENT MERGE Description: ============ This patch address the following issue: 1. The SURGERY file (#130) ADT and ARS cross references do not merge during a patient merge. Associated Ticket(s): ===================== 1. I8053319FY16 - AEU reports the site had a patient merge but the surgery information did not transfer with the account. I8152707FY16 (d) R8089319FY16 (d) I9201527FY16 (d) Associated NSR(s): ================== N/A Participating Test Sites: ========================= Manchester VAMC Lebanon VAMC Ticket Overview: ================ 1. I8053319FY16 - AEU reports the site had a patient merge but the surgery information did not transfer with the account. Patient Safety Issues: ---------------------- PSPO00003176: The Patient Merge software must have full interoperability with all other VistA packages, such as Surgery and Radiology. Problem: -------- The SURGERY file (#130) ADT and ARS cross references do not merge during a patient merge. These cross references have a non-standard PATIENT (#2) file pointer. The merging of a non-standard PATIENT file (#2) pointer during a patient merge should have been handled by the file developers but were not. Post install routine SR3189P will remove the old cross references. Resolution: ----------- The Data Dictionary for the SURGERY (#130) file was modified to delete the old Traditional style "ADT" and "ARS" xrefs and create New style "ADT" and "ARS" indexes. The "ADT" index be will updated any time the PATIENT (#.01) or DATE OF OPERATION (#.09) fields are modified in the SURGERY (#130) file. The "ARS" index will be updated any time the PATIENT (#.01), ASSESSMENT STATUS (#235), or ASSESSMENT TYPE (#284) fields are modified in the SURGERY (#130) file. Files & Fields Associated: File Name (Number) Field Name (Number) Change ------------------ ------------------- --------- Surgery (#130) PATIENT (#.01) Modify Surgery (#130) DATE OF OPERATION (#.09) Modify Surgery (#130) ASSESSMENT STATUS (#235) Modify Surgery (#130) ASSESSMENT TYPE (#284) Modify Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Surgery/Patches/SR_3.0_189

Patch Subject: VISTA SCHEDULING ENHANCEMENTS Description: ============ VS GUI v2.0.0.8 and this patch provide the 'Additional Enhancements' to the VistA Scheduling (VS) Graphical User Interface (GUI) v2.0.0.5 application which were requested by Office of Veteran Access to Care (OVAC), as well as fixes to 35 CA SDM tickets. These additional enhancements will provide greater flexibility in the scheduling process, provide the ability to manage requests more efficiently and effectively, synchronize patient information between VS GUI and VistA Scheduling Legacy, improve the printing process, save time by cleaning up unresolved requests, contact patients for appointments more effectively and efficiently and improve performance. ENHANCEMENTS Epic #1-Grid Match and Unscheduled Appointments For VSE Schedulers who schedule a series of appointments for a Veteran. The solution provides the scheduler with the ability to schedule appointments at times and with the variations needed to support clinic operation, as well as identifying the exact appointment times for unscheduled patients/walk-ins. That helps provide greater flexibility in scheduling Veterans. Unlike the current system that does not offer the flexibility needed, our process increases availability and provides better tracking information. Epic #2-Edit and View Requests For VSE Schedulers who schedule appointments in VSE. The solution allows schedulers to manage requests more efficiently and effectively by editing requests, saving and viewing all comments, and re-opening requests as needed while always preserving the original preferred date (PD). That helps the scheduler make appointments for Veterans without having to create a new request and ensures that Veterans receive care when needed. Unlike the current system that will not allow the scheduler to edit some critical request information and will not re-open requests for no show and canceled by patient appointments, our process allows schedulers to more effectively view and edit requests, which will improve the accuracy and efficiency of the scheduling process. Epic #3-Demographic Data Updates For VSE Schedulers who schedule appointments within VS GUI, the solution allows the scheduler to update information in VS GUI and the correct information will be updated in VistA. That helps the scheduler better serve the Veteran by making updates more efficiently and while making an appointment for the Veteran. Unlike the current system that forces the scheduler to move back and forth between VS GUI and VistA, reducing the likelihood that schedulers will want to use VS GUI and increasing the time to make changes, our process reduces the time the scheduler needs to update important Veteran demographic information because the scheduler can update the Veteran's demographic information while making appointments and without having to use the VistA system. Epic #5-CCOW and Patient Identification For VSE Schedulers who schedule appointments in VSE, the solution synchronizes the patient information across functional areas within VSE to the patient in focus and provides more information about a patient's identification in the calendar view of appointments. That helps the scheduler search for and view patient appointments more efficiently and consistently. Unlike the current process where the scheduler has to search on the patient in each application, independently, and doesn't have enough information for identifying appointments in the calendar, our process allows schedulers to more effectively manage appointments. Epic #7-Improved Printing For VSE Schedulers, providers, and patients who need to print or read printed schedules and scheduling letters (clinic cancellation, appointment cancellation, no-show, and pre-appointment), the solution enables improved printing of letters and printing of Veteran appointments. That provides printing of letters with visually effective formatting, no loss of information, and provides printing of appointments for Veterans -- unlike the current VSE system that has issues printing all types of letters and schedules. Our process improves the processes related to printing in VSE. Epic 9-Trash Queue Cleanup For administrators who need to identify and purge unresolved requests, the solution allows a task to be run to identify open appointment requests or duplicate appointment requests and close them, producing a report for administrators. Note: Excludes VAR requests which are called Veteran Request or Mobile and Welcome to VA (W2VA) requests - all stored in the SDEC APPT Request file. That helps the administrator by rectifying unresolved requests automatically. Unlike the current process where there are duplicate requests and unresolved requests that must be resolved by the administrator, our process saves schedulers and administrators time but still allows them to review closed duplicates and open requests. Epic 10- For VSE Schedulers who need to create and view Veteran, appointment, and clinic information in VSE, the solution allows the user to set their default view preferences and adds a view only option. That helps to improve scheduler efficiency, unlike the current VSE system that does not provide these features. Our process improves the processes used by schedulers and improves overall service to the Veteran. Epic 11-Veterans Appointment Request (VAR) Queue For VSE Schedulers who schedule appointments in VSE, the solution displays the telephone number that was entered into the VAR screen by the Veteran in the VAR queue. That helps to ensure the scheduler will be contacting the Veteran at the number they have provided, unlike the current process where the phone number entered into VAR does not display in VSE. Our process allows schedulers to more efficiently and effectively contact patients for appointments. Epic 13- For all VSE users who view, schedule, or manage information in VSE, the solution provides efficient and effective response time, displaying pick lists, query results, and reports real time and without performance issues such as white screens or a seemingly endless hourglass. That helps to ensure the scheduler is able to serve Veterans efficiently and effectively, maintaining good productivity. Unlike the current process that pulls up limited data, takes too long to pull up data, or results in white screens, the solution allows VSE to display pick lists in five (5) seconds or less. VSE informs user of progress during the generation of queries. Our process allows schedulers to more efficiently and effectively perform their jobs. CA SDM TICKETS I10691629FY16- User can select a different patient from the calendar (PSPO 3242) I11142558FY17- Comments in VS GUI do not work properly; there are differences between VistA and VS GUI; includes NOTES & Comments that are in different fields in the GUI (PSPO 3306) I10665102FY16- Availability does not zero out I10320124FY16- Scheduling letters printed with the default font of 15 do not print the information correctly on the page. I9982851FY16- VSE Grid displaying incorrect slot availability I10449686FY16- ASH: VS GUI displays too many slots for a 60min increment clinic R10131762FY16- VS GUI Not Prompting for Overbook I9871873FY16- VSE Calendar is not displaying the Overbook symbol beside the overbook appointment. I10659119FY16- VSE is not displaying the RM GRID in the correct Priority Order I9674926FY16- The Patient Address is too high on the letter to fit into a #10 standard one window envelope. I10043597FY16- The length of the Special Needs and Preferences REMARKS field in VS GUI is causing unresponsive system. I10619212FY16- All requests in the VS Request Grid should open to TODAYs Date when the CID/PD Date is in the PAST. I9937259FY16- Comments entered in the VS GUI APPT Request are not being displayed when the Request is Viewed and they are not transferring to the EWL Request. I10695144FY16- New or Established field is not calculating according to Business Rules set by ACAP office. I11146466FY17- Need the ability to make a scheduled appointment at a time that overlaps an already scheduled appointment. (ex - Tele-Health) I9883746FY16- MRTC not reflecting correct CID Date I9654231FY16- Multi-Appointment booking in VSE GUI - incorrect CID being passed to VistA I10573215FY16- Multiple Return To Clinic (MRTC) is allowing the clinic to be changed to a clinic that is not within the same stop code as the requested clinic I9883550FY16- If the user does not complete the steps when cancelling a MRTC appointment, the appt is not completely cancelled. I9642120FY16- During the process of Multi-Book appointment booking, the VS GUI hangs. I9829412FY16- ENH REQ Approved: MULTIPLE APPOINTMENT BOOKING-SDMULTIBOOK Option- Appts MADE in VistA Legacy are not reflected in VS GUI. I9956180FY16- Edits made to request comments in VS GUI do not get sent to VistA legacy. I9568671FY16- CONSULTS ENTERED PRIOR TO PATCH GMRC*81 VSE IS USING CURRENT DATE AS CID I9381748FY16- Query for Recall results with black screen and application freezing. I9878547FY16- VSE keeps freezing at many points from log in to well within the program. I11145711FY17- Consults are to be displayed in the RM Grid regardless of the request date I10612450FY16- Calendars in the Schedules Section do not sync together I10645706FY16- Month View in Schedules Section is not functioning properly I10659319FY16- VS GUI is not reflecting the SC Related field in the RM GRID correctly. I10644445FY16- Editing an Appt Request leaves Clinic/Service field blank I10371353FY16- Address in the New Appointment block under the Contact Tab is displaying the Next Of Kin - city, state, zip instead of patient address information I10046473FY16- Large Amount of Characters in Notes Section causes an error in VS GUI Appt Remarks after entering an Appt I9961448FY16- Entering a "^" when creating an appointment request in VS GUI causes a table error box and user cannot correct. I10644588FY16- Viewing EWL Request is not displaying Clinic/Service field I11611508FY17- When using the VS GUI, the user currently has no indication whether he is connected to a test or production environment. An indication must be provided the user when connected to a test environment. I12577233FY17- There are differences between VistA and VS GUI regarding NOTES and Comments that do not match. I2596663FY17- SDAM Appointment Management errors when a user replies 'YES' to the prompt "WANT PATIENT NOTIFIED OF LAB, X-RAY, OR EKG STOPS?" I2524606FY17- The DATE APPT MADE and DATA ENTRY CLERK fields of the HOSPITAL LOCATION Appointment record and the PATIENT Appointment record are being over-written when an appointment is Cancelled. Patch Components: ----------------- Files & Fields Associated: File Name (#) Field Name (#) New/Modified/Deleted ------------- -------------- -------------------- RECALL REMINDERS COMMENT Modified (#403.5) (#2.5) RECALL REMINDERS FAST/NON-FASTING Modified (#403.5) (#2.6) RECALL REMINDERS TEST/APP. Modified (#403.5) (#3) RECALL REMINDERS PROVIDER Modified (#403.5) (#4) RECALL REMINDERS CLINIC Modified (#403.5) (#4.5) RECALL REMINDERS LENGTH OF APPT. Modified (#403.5) (#4.7) SD WAIT LIST WL APPOINTMENT TYPE Modified (#409.3) (#8.7) SD WAIT LIST REQUEST BY Modified (#409.3) (#11) SD WAIT LIST PROVIDER Modified (#409.3) (#12) SD WAIT LIST COMMENTS Modified (#409.3) (#25) SDEC APPT REQUEST PATIENT STATUS Modified (#409.85) (#.02) SDEC APPT REQUEST REQ SPECIFIC CLINIC Modified (#409.85) (#8) SDEC APPT REQUEST REQ SERVICE/SPECIALTY Modified (#409.85) (#8.5) SDEC APPT REQUEST REQ APPOINTMENT TYPE Modified (#409.85) (#8.7) SDEC APPT REQUEST REQUESTED BY Modified (#409.85) (#11) SDEC APPT REQUEST PROVIDER Modified (#409.85) (#12) SDEC APPT REQUEST (DISPOSITION CLOSED BY CLEANUP New (#409.85) (#21.1) SDEC APPT REQUEST CURRENT STATUS Modified (#409.85) (#23) SDEC APPT REQUEST COMMENTS Modified (#409.85) (#25) SDEC RESOURCE ABBREVIATION New (#409.831) (#.011) Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- SDEC INITIAL CLEANUP UTILITY run routine New SDEC REQ REOPENED BY SDCANCEL run routine New Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- SDEC DEFAULT FONT SIZE New SDEC REQ MGR GRID FILTER New Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Remote Procedures Associated: RPC Name New/Modified/Deleted -------- -------------------- SDEC APPADD Modified SDEC ARGET Modified SDEC GETREGA Modified SDEC PTLOOKRS Modified SDEC PTSET Modified SDEC RECGET Modified SDEC REQGET Modified SDEC WLGET Modified SDEC01 CLINICS New SDEC57 OBM New SDECAR3 AREDIT New SDECDEM MARITAL New SDECDEM RELIGION New SDECDEM ZIPLINK New SDECDEV DEV New SDECDEV PRINT New SDECRMGP GETRMGUP New SDECRMGP PUTRMGUP New SDECU4 GETFONT New SDECU4 PUTFONT New Security Keys Associated: Security Key Name ----------------- SDECVIEW Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A New Service Requests (NSRs): ---------------------------- N/A Additional Information: N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. I10691629FY16- User can select a different patient from the calendar (PSPO 3242) Problem: ------- When a user searches and selects a patient and clicks on an appointment in the calendar for a different patient, this action changes the patient in the Ribbon Bar to the new patient information but leaves the RM grid with the original patient. Resolution: ---------- The Client has been updated to redisplay both the Patient and Patient's Requests when an appointment is selected from the calendar. 2. 11142558FY17- Comments in VS GUI do not work properly; there are differences between VistA and VS GUI; includes NOTES & Comments that are in different fields in the GUI (PSPO 3306) Problem: ------- Several clerks had noted that the comment system in VS GUI does not work properly compared to VistA. Comments are appearing in different places or occasionally not at all. One clerk in particular was attempting to show the differences between VSE/VistA and we came across a comment "follow-up required within 7-10 days" that appeared in VistA but not VSE. This particular clinic may have over 300 interactions with patients per day so a comment like that getting lost could lead to follow-ups potentially being scheduled outside the requested window. Resolution: ---------- The SDEC APPADD RPC has been updated to properly store the NOTE into the Patient's appointment record. The SDECADD routine has been updated to properly store to the NOTE multiple of the SDEC APPOINTMENT file (#409.84) when an appointment is added or updated from VistA. 3. I10665102FY16- Availability does not zero out Problem: ------- When an appointment is booked at 815-915am in VistA for a clinic that has availability from 0800-0900, in VistA the 8am slot still shows 1 and at 815 it shows an *. In VS GUI, the slot still shows 1 from 8-9 and there is no *. Resolution: ---------- The client has changed the handling of the data returned from the SDEC APPSLOTS rpc to insure the corrected availability is displayed in the Clinic Schedule. 4. I10320124FY16- Scheduling letters printed with the default font of 15 do not print the information correctly on the page. Problem: ------- Users want to be able to change the font size when printing letters and be able to set the default font size so they do not have to reset it every time an appointment letter is printed. Resolution: ---------- A new PARAMETER DEFINITION (XPAR) has been added called SDEC DEFAULT FONT SIZE which will hold the default Font. Two new RPCs have been added - - SDECU4 GETFONT allows the VS GUI to get the current default font size. - SDECU4 PUTFONT allows the VS GUI to set a new default font size to the new XPAR. 5. I9982851FY16- VSE Grid displaying incorrect slot availability. Problem: ------- There is an issue where several clinic grids are not displaying the correct slot availability. Resolution: ---------- The GUI client has been updated to correctly size the Appointment Time slots to display at the slot start time and over the duration of the slot. 6. I10449686FY16- VS GUI displays too many slots for a 60min increment clinic. Problem: ------- VS GUI displays too many slots for a 60min increment clinic. In VistA, users only see 1 slot per hour whereas in VS GUI users see 2 slots per hour (1 per 30min slot). Resolution: ---------- The GUI client has been updated to correctly size the Appointment Time slots to display at the slot start time and over the duration of the slot. 7. R10131762FY16- VS GUI Not Prompting for Overbook Problem: ------- VS GUI does not follow the same rules as VistA when determining if a prompt for Overbook should occur. Resolution: ---------- A new RPC has been added, SDEC57 OBM, which uses the same rules for determining when an overbook status has occurred and what message should be displayed to the user. 8. I9871873FY16- VSE Calendar is not displaying the Overbook symbol beside the overbook appointment. Problem: ------- When a Scheduling User has the SDMOB security key, that user can overbook appointments outside the scheduling grid hours. When the appointment is booked after the normal work hour, the overbook symbol is not present in the VSE GUI beside the appointment. Example: if a clinic is set up for working hours from 8am - 4pm and an overbook apt is made at 8pm - the VSE GUI the displays the patient name and appointment at the 8 pm slot but the overbook symbol is displayed at 5pm. Resolution: ---------- The GUI client has been updated to change the handling of the return from the SDEC APPSLOTS rpc to insure the overbook symbol is displayed in the Clinic Schedule. 9. I10659119FY16- VSE is not displaying the RM GRID in the correct Priority Order. Problem: ------- The correct default sort is as follows: 1. Requests with blank Priority Group 2. Priority Group 1 OR all patients whose request for care is SC related (Field #409.3,15 = YES). Display records with SCVisit=Yes first followed by SCVisit=Null. 3. Priority Group 2 whose request for care is NOT SCVisit then Priority Group 3 and if Priority Group 3 is not SCVisit .. and so on. 4. For ascending Priority Group order within each group, the system shall sort the requests by the desired date, and within each desired date, the system shall sort the requests by the date the request was made. Resolution: ---------- For EWL and APPT request types, SC Related is determined by the SERVICE CONNECTED PRIORITY field. This field is found in both SD WAIT LIST and SDEC APPT REQUEST files. Note that Groups 2-8 are treated like GROUP 1 if SERVICE CONNECTED PRIORITY is 'YES', so they could end up mixed with no order to the GROUP. For Recall and Consults, SC Related is defined as if it were 'YES' for GROUP 1 and Null for all others. '... for Recall and Consult for all other Priority groups it should be null. For Priority Group 1 it will be Yes.' 10. I9674926FY16- The Patient Address is too high on the letter to fit into a #10 standard one window envelope. Problem: ------- When printing patient letters from VS GUI, the Patient Address is too high on the letter to fit into a #10 standard one window envelope. When you print in VISTA to a network printer, it's fine. Resolution: ---------- This has been found to be a Windows issue, therefore when printing letters that need to go into a #10 window envelope, these letters should be printed from within VistA. 11. I10043597FY16- The length of the Special Needs and Preferences REMARKS field in VS GUI is causing unresponsive system. Problem: ------- There is a problem with the Remarks section in the special needs and preferences in VS GUI. If there are too many characters (no max set) the system will give the white screen and users will need to close out. Resolution: ---------- Although the REMARKS field (#6) of the SDEC PREFERENCES AND SPECIAL NEEDS file (#409.845) is a Word Processing field, the string coming in is being stored as only 1 line no matter how long it is. This could cause the entry to exceed the maximum allowed string length. This has been corrected by dividing the string into multiple lines with a maximum line size of 80 characters. 12. I10619212FY16- All requests in the VS Request Grid should open to TODAYs Date when the CID/PD Date is in the PAST. Problem: ------- All Request in the VS GUI Request Grid should open to TODAYs Date when the CID/PD Date is in the PAST. Currently the calendar opens to the CID/PD Date in the Request (APPT, EWL, RECALL, CONSULT). This is causing confusion at the sites and possible incorrect scheduling. Making all requests work the same way will eliminate confusion and possible incorrect scheduling. Resolution: ---------- The GUI client has been updated to open the calendar to Todays Date when the CID (preferred date) is in the past. 13. I9937259FY16- Comments entered in the VS GUI APPT Request are not being displayed when the Request is viewed and they are not transferring to the EWL Request. Problem: ------- The Comments field in the Appointment Dialog for VS GUI contains important information concerning the Appointment being requested. This comment is added to the APPT Request but is not being displayed when the user selects the VIEW REQUEST function from the request grid. Also, when the function to transfer the APPT Request to the EWL Request, the comments are not transferring to the EWL Request. Resolution: ---------- The SDEC APPADD rpc has been updated to pass the comment all the way through to the appropriated Appointment Request, Patient Appointment, and Clinic Appointment. 14. I10695144FY16- New or Established field is not calculating according to Business Rules set by ACAP office. Problem: ------- Currently the VS GUI is looking at the specific CLINIC but it should be looking at the Primary Stop Code of the Clinic to determine NEW or ESTABLISHED status. Per Dr. Davies comment in the Issue Report - the definition of 'established' that we have in place now is simply those patients who have completed at least one appointment in a given stop code in the past 24 months. I agree that it is logical to use check out since I presume that is the data element indicates they have completed at least one appointment in the stop code. Resolution: ---------- The SDEC PCST2GET rpc has been updated to use the Clinic Stop code in place of the Clinic id AND also has been updated to use the check-out time instead of the appointment time to determine if the patient is 'NEW' or 'ESTABLISHED'. 15. I11146466FY17- Need the ability to make a scheduled appointment at a time that overlaps an already scheduled appointment. (ex - Tele-Health) Problem: ------- In the current VistA scheduling application the user is able to enter a scheduled appointment at a time that is not consistent with the allocated time slots. Example - A slot is allocated at the top hour with the appointment length of one hour at 9, 10, and 11. The user needs to make a scheduled appointment at 9:10. The VSE GUI needs to add the capability to enter the appointment time when scheduling an appointment. The entered appointment time must display accurately in the calendar grid. Resolution: ---------- The VS GUI client has been updated to allow booking and overlap appointment. 16. I9883746FY16- MRTC not reflecting correct CID Date Problem: ------- When cancelling an MRTC appointment, if the user selects cancel by patient and enters a different CID date, the Child request reopens with the original CID date. When the appointment is rescheduled the calendar opens to original CID date. And after scheduling the appointment and viewing the appointment details in Vista the CID date is showing the same date as the re-scheduled appointment date. Resolution: ---------- The GUI client has been updated to correct the MRTC process that was not reflecting the correct CID Date. When cancelling an appointment by patient that is part of an MRTC, and the the CID date is changed, the new CID date is not reflected in the re-opened appt request. 17. I9654231FY16- Multi-Appointment booking in VSE GUI - incorrect CID being passed to VistA Problem: ------- When Multi-Appointments (MRTC) are booked in the VSE GUI. each appointment made has its own request with a calculated CID/Preferred Date. The CID/Preferred Date that is being set in VSE is not the same as what is being shown in VistA. Resolution: ---------- The GUI client has been updated to pass the correct CID to the SDEC APPADD rpc. 18. I10573215FY16- Multiple Return To Clinic (MRTC) is allowing the clinic to be changed to a clinic that is not within the same stop code as the requested clinic Problem: ------- In VS GUI, Multiple Return To Clinic (MRTC) is allowing the clinic to be changed to a clinic that is not within the same stop code as the requested clinic. This could result in the patient not getting the kind of care/appointment that the provider requested. Resolution: ---------- A new rpc has been added called SDEC01 CLINICS which will return a list of clinics for a given CLINIC STOP code or that match a given clinic. The GUI client has been updated to use the new SDEC01 CLINICS rpc to fill the combo box with clinics having matching stop codes. 19. 9883550FY16- If the user does not complete the steps when cancelling a MRTC appointment, the appt is not completely cancelled. Problem: ------- If the user does not complete the steps when cancelling a MRTC appointment, VSE is not cancelling all of the functions. This is allowing the user to attempt to start the cancellation over in the same transaction which is causing an error. Resolution: ---------- The GUI client has been updated to improve the flow of cancelling an MRTC appointment so that the cancellation is completed correctly. 20. I9642120FY16- During the process of Multi-Book appointment booking, the VS GUI hangs. Problem: ------- There are times when VS GUI hangs during the process of adding a Multi-Book appointment. This seems to be due to unrecognized overbook messages. Resolution: ---------- The GUI Client has been updated to handle all overbook messages and removed the inappropriate messages. 21. I9829412FY16- ENH REQ Approved: MULTIPLE APPOINTMENT BOOKING-SDMULTIBOOK Option- Appts MADE in VistA Legacy are not reflected in VS GUI. Problem: ------- In MULTIPLE APPOINTMENT BOOKING - SDMULTIBOOK option - Appointments MADE in VistA are not showing in the calendar for VS GUI. Resolution: ---------- The SDMULTIBOOK option has been updated to store the new appointment data into the SDEC APPOINTMENT file and to add an entry to the SDEC APPT REQUEST file when appropriate 22. I9956180FY16- Edits made to request comments in VS GUI do not get sent to VistA legacy. Problem: ------- If a user edits the Notes field of the Appointment Dialog in VS GUI, the edit is not sent to VistA. The Notes field of the Appointment Cancel dialog also is not sent to VistA. The appointment request will reopen on the request grid and the comments will not reflect the edit, only the original notes entered when the initial creation of the appointment was performed. Resolution: ---------- The SDEC EDITAPPT RPC has been updated to store the edited Note to the Clinic Appointment record. 23. I9568671FY16- VS GUI should be updated to always show the CID Date on the RM Grid for Consults. Problem: ------- GMRC*3*81 made changes to some fields that VS GUI is referencing and VS GUI needs to be updated. The VS GUI should always show the CID Date found in the Consult. This will need to be coded to start this process as of the compliance date of the patch. Current requirements are - In OT3, there is a requirement for Consult that If the 'Entered Date' and 'Earliest Appropriate Date' (both from the Consult in CPRS) are equal to each other then VS GUI shall use the 'Urgency' field for CID unless the Urgency field is equal to 'Stat' or 'Next Available', 'Emergency' or 'Today' then use 'Earliest Appropriate Date' as the CID. Resolution: ---------- The SDEC REQGET RPC has been updated to check that GMRC*3.0*81 has been installed on or before the File Entry Date (and time). If so, we always return the 'EARLIEST DATE' (CLINICALLY INDICATED DATE) as the 9th return piece (PRIO). If GMRC*3.0*81 has not been installed by the FILE ENTRY DATE, we execute the same logic as before, which is: If the 'Entered Date' and 'Earliest Appropriate Date' (both from the Consult in CPRS) are equal to each other then VS GUI will use the 'Urgency' field for CID unless the Urgency field is equal to 'Stat' or 'Next Available', 'Emergency' or 'Today' then use 'Earliest Appropriate Date' as the CID. 24. I9381748FY16- Query for Recall results with black screen and application freezing. Problem: ------- When using the Query Tool in VS GUI to submit a data request that includes a clinic filter causes the screen to go black and there is a delay of 2-3 minutes before the results are returned. Resolution: ---------- This has been addressed in the SDEC RECGET RPC by using the existing E xref in the RECALL REMINDERS file (#403.5) to look up by Clinic when a Clinic ID is included in the filters. 25. I9878547FY16- VSE keeps freezing at many points from log in to well within the program. Problem: ------- VS GUI freezes and displays a white or black screen at various points in the application. Resolution: ---------- Additional cross-references have been added to some of the VS GUI related files along with support from the VS GUI related APIs to speed up searches from the RM Grid. The GUI Client has been updated to use multi-threading for several processes that tend to take more time than is acceptable. 26. I11145711FY17- Consults are to be displayed in the RM Grid regardless of the request date Problem: ------- All Pending Consults should be displayed in the RM GRID regardless of the Request Date. Resolution: ---------- The 365 day restriction has been removed from the SDEC REQCHK and SDECRMG RMG RPCs. 27. I10612450FY16- Calendars in the Schedules Section do not sync together Problem: ------- In VS GUI, if the user is viewing/selecting clinics in the Clinic Schedules versus selecting a request type and changes clinics, whatever date the previous clinic was on will remain showing in the calendar on the left. The grid and calendar located in the grid will default to today's date. Resolution: ---------- The GUI Client has been updated to correct the calendar sync when the user changes clinics and when the CID is in the past. 28. I10645706FY16- Month View in Schedules Section is not functioning properly Problem: ------- Changing to a Month View and then selecting the triangle within the day slot, opens the wrong date. Resolution: ---------- The GUI Client has been corrected to display the correct date when selecting the triangle within the day slot. 29. I10659319FY16- VS GUI is not reflecting the SC Related field in the RM GRID correctly. Problem: ------- In the VS GUI the SC Related field on the RM Grid is not reflecting the SERVICE CONNECTED PRIORITY field of the VS GUI Request. Resolution: ---------- The SCVisit value was not getting updated when the record was read going into the Request Management screen. This has been corrected. 30. I10644445FY16- Editing an Appt Request leaves Clinic/Service field blank Problem: ------- When editing an appointment request the clinic/service field is blank when the Appointment Request box opens. Matching clinic names are appearing in a separate window outside of the appointment request box versus under the clinic/service box. The box allows the user to highlight a clinic name but the name does not populate the clinic/service field. Resolution: ---------- The GUI Client has been updated to properly display the data in the clinic/service field AND when selecting a clinic, the matching clinic names display under the clinic/service box as expected. 31. I10371353FY16- Address in the New Appointment block under the Contact Tab is displaying the Next Of Kin - city, state, zip instead of patient address information Problem: ------- The Address that is in the Contact Information in the Add Appointment dialog is not the same as the one that displays in the demographics area. Further researched shows that the Contact Information is pulling the Address from the Next Of Kin address. Team is evaluating to determine if this was a requirement or a potential enhancement request. Resolution: ---------- The GUI Client has been updated to pull the correct patient address data for the Contact Information and the Demographics area. 32. I10046473FY16- Large Amount of Characters in Notes Section causes an error in VS GUI Appt Remarks after entering an Appt Problem: ------- In the Notes field of New Appointment dialog the user/scheduler can enter 3000+ characters; however, the text is filing to Other field of the Appointment Sub-file and that field is limited to only 150 characters of text. If the scheduler does add a large amount of text then VS GUI will register an unable to load dialog error when OK is selected in New Appointment dialog and the application will freeze up. Resolution: ---------- Modified New Appointment dialog to limit Notes to 150 characters. 33. I9961448FY16- Entering a "^" when creating an appointment request in VS GUI causes a table error box and user cannot correct. Problem: ------- VistA does not allow the use of this symbol '^' when entering comments into the other field inside of appointment management. However it will notify and allow the user to re-enter the comments. When using this symbol in VS GUI in an appointment request, a table error box is received and the user is not given the opportunity to correct. The request completes and comments are not reflected. When using this symbol while scheduling an appointment, in the Notes the user is given the table error. The user is not given the opportunity to correct. The new appt box closes. Pending appointments show the scheduling appt however the user is not able to select the appt to display the grid or choose that clinic date using the scheduling section and manually entering the clinic and selecting the day on the calendar. The grid appears grayed out and the same table error is received. Resolution: ---------- The SDEC WLSET, SDEC ARSET, and SDEC RECSET RPCs have been updated to check for these ^ characters during input validation. If the ^ character is detected, it is changed to a space. 34. I10644588FY16- Viewing EWL Request is not displaying Clinic/Service field Problem: ------- When viewing an EWL Request the Clinic/Service field is not populated. This issue is happening because the first part of the clinic name is the same for multiple clinics. For example, CHY ORTHO PECKHAM, CHY ORTHO PECKHAM RETURN, CHY ORTHO PECKHAM WALK IN. Resolution: ---------- The GUI Client has been updated to correctly search and display Clinic names. 35. I11611508FY17- When using the VS GUI, the user currently has no indication whether he is connected to a test or production environment. An indication must be provided the user when connected to a test environment. Problem: ------- When running VS GUI, there is no indication if the application is live or still in a test environment. The system must let the user know they are connected to the test environment. Resolution: ---------- The GUI Client has been updated to display the text 'TEST PRODUCTION' or 'PRODUCTION ENVIRONMENT' in the header based on the Sign-on flag [7]. 'PRODUCTION ENVIRONMENT' displays in RED and 'TEST PRODUCTION' displays in black on a white background. 36. I12577233FY17- There are differences between VistA and VS GUI regarding NOTES and Comments that do not match. Problem: ------- The OTHER field (#3) that is in the HOSPITAL LOCATION file (#44) under the APPOINTMENT multiple field (#1900) and then under the PATIENT multiple field (#2) is not populated from the SDEC APPADD rpc if the text has exceeded the 150 character limit. From VistA appointment management (SDAM), when an appointment is added or cancelled and if the user enters text in the OTHER INFO prompt, the NOTE field (#1) in the SDEC APPOINTMENT file (#409.84) is not being populated. Resolution: ---------- The SDEC APPADD rpc has been updated to limit the note to 150 characters so that the 150 character limit is not exceeded. The VistA Appointment Management option has been updated to include the OTHER INFO comment when calling the update for the SDEC APPOINTMENT file (#409.84). The post-installation routine SDEC658 will Schedule a one time Taskman job that will sync the OTHER field (#3) under the PATIENT multiple field (#2) for the APPOINTMENT multiple field (#1900) in the HOSPITAL LOCATION file (#44) with the NOTE field (#1) in the SDEC APPOINTMENT file (#409.84). A report will be provided via Mailman to the person installing the patch once the Taskman job finishes. This report will show the differences between the 2 fields and how they were resolved. The subject of the Mailman message will be: "SD*5.3*658 NOTE UPDATE REPORT DATA for <date>". 37. I2596663FY17- SDAM Appointment Management errors when a user replies 'YES' to the prompt "WANT PATIENT NOTIFIED OF LAB, X-RAY, OR EKG STOPS?" Problem: ------- Changes made to accommodate the MULTIPLE APPOINTMENT BOOKING [SDMULTIBOOK] option are causing an error at the "WANT PATIENT NOTIFIED OF LAB, X-RAY, OR EKG STOPS?" prompt due to the SL variable being killed when the date/time is being collected for this prompt. Resolution: ---------- The SDAM Appointment Management has been updated to re-initialize the SL variable if needed. 38. I2524606FY17- The DATE APPT MADE and DATA ENTRY CLERK fields of the HOSPITAL LOCATION Appointment record and the PATIENT Appointment record are being over-written when an appointment is Cancelled. Problem: ------- The DATE APPT MADE field (#8) and the DATA ENTRY CLERK field (#7) in the HOSPITAL LOCATION file (#44) under the APPOINTMENT multiple field (#1900) and under the PATIENT multiple field (#2) are being overwritten with the current date/time and user if a REMARK is entered. Also, the DATE APPT MADE field (#20) and the DATA ENTRY CLERK field (#19) in the PATIENT file (#2) under the APPOINTMENT multiple field (#1900) are being overwritten with the current date/time and user if a REMARK is entered. Resolution: ---------- The Set Note logic used by the SDEC APPDEL rpc has been corrected to not change the DATA ENTRY CLERK fields and the DATE APPT MADE fields. Test Sites: ---------- VA Hudson Valley Health Care System Chillicothe VA Medical Center Asheville VA Medical Center Louis Stokes Cleveland VA Medical Center Southern Arizona VA Health Care System Software and Documentation Retrieval Instructions: ---------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ Title File Name SFTP Mode ------------------------------------------------------------------------- SCHEDULING User Manual VSE_UG.PDF (binary) SCHEDULING User Manual VSE_UG.DOCX (binary) SCHEDULING Technical Manual VSE_TM.PDF (binary) SCHEDULING Technical Manual VSE_TM.DOCX (binary) SCHEDULING Security Guide VSE_SG.PDF (binary) SCHEDULING Security Guide VSE_SG.DOCX (binary) SCHEDULING Install Guide VSE_Install_Guide.DOCX (binary) Patch Installation: Pre/Post Installation Overview: ------------------------------- This patch contains no PRE Installation processing. Post-Installation processing does the following: 1. Registers the new APIs to the SDECRPC option. 2. Builds new cross-references. 3. Populates the new ABBREVIATION field (#.011) in the SDEC RESOURCE file (#409.831). 4. Adds the new SDEC REQ REOPENED BY SDCANCEL option to the SDOUTPUT menu. 5. Schedule a one time Taskman job that will sync the OTHER field (#3) under the PATIENT multiple field (#2) for the APPOINTMENT multiple field (#1900) in the HOSPITAL LOCATION file (#44) with the NOTE field (#1) in the SDEC APPOINTMENT file (#409.84). A report will be provided via Mailman to the person installing the patch once the Taskman job finishes. This report will show the differences between the 2 fields and how they were resolved. The subject of the Mailman message will be: "SD*5.3*658 NOTE UPDATE REPORT DATA for <date>". Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Scheduling/Patches/SD_5.3_658

Patch Subject: CLEANUP OF SOCIAL SECURITY NUMBERS IN INCOME PERSON (#408.13) FILE Description: ============ This patch addresses Your IT Services incident INC1928289 to fix a critical defect introduced by Enrollment System (ES) 5.3 and corrected by 5.3.0.070001, where the dependent Social Security Number (SSN) data at the Veterans Health Information System and Technology Architecture (VistA) facilities was corrupted and requires a VistA patch to clean up the database corruption. Please refer to the 'Defect Tracking System Ticket(s) & Overview' section of this patch for a description of the problem and its resolution. This patch is a follow-up patch to DG*5.3*970 and it is required to install this patch. Patch DG*5.3*970 created global ^XTMP("DG53970P") which lists the dependent records' Internal Entry Numbers (IENs) in the INCOME PERSON file (#408.13) that need to have the SOCIAL SECURITY NUMBER (#.09) field updated. It also lists the record number (DFN) in PATIENT (#2) file for the patient associated with the dependent record. Patch IVM*2.0*174 uses this global when processing the Health Level 7 (HL7) ORU-Z10 message from ES to update the SOCIAL SECURITY NUMBER (#.09) field of dependent records in the INCOME PERSON file (#408.13) and to clean them out of the ^XTMP("DG53970P") global. Additionally, a post-install routine extends the expiration date of the ^XTMP("DG53970P") global by an additional 120 days from the patch install date and submits a background job to send a MailMan message every 2 days to report the status of IENs and DFNs remaining in the ^XTMP global. The message is sent to FORUM MailMan group [email protected]. The members of the mail group consist of developers, Software Quality Assurance (SQA), and Health Product Support. A copy of the mail message will be sent to the installer of patch IVM*2.0*174. Once all dependent records identified in the ^XTMP("DG53970P") global have had the SOCIAL SECURITY NUMBER (#.09) field of the INCOME PERSON file (#408.13) successfully updated, the background job will no longer be automatically queued to check the global and send a status message. Listing of Updates: =================== Patch IVM*2.0*174 modifies the processing of the HL7 ORU-Z10 message from ES as follows: 1. If the Patient record from the ORU-Z10 PID segment is found in the ^XTMP("DG53970P") global, only the ZDP segments in the message are processed as follows: a. The dependent record (Internal Entry Number) from the INCOME PERSON file (#408.13) is derived from the ZDP segment. If that record is found in the ^XTMP("DG53970P") global, the SSN from the ZDP segment is filed into the INCOME PERSON file (#408.13) for that dependent. b. The SSN will be validated prior to filing and will not be filed if it is invalid. The SSN must be 9 numbers. c. If the ZDP segment includes a PSEUDO SSN REASON and it is a valid value of "S", "N", or "R", it is stored in the INCOME PERSON file (#408.13) in the PSEUDO SSN REASON field (#.1) and a "P" is appended to the SSN prior to being filed. d. Prior to the SSN being updated, the SSN field in the INCOME PERSON file (#408.13) is checked and will be corrected if the field is corrupted. e. If the filing of the SSN fails, the error message is placed in the ^XTMP("DG53970P") global. f. If the filing of the SSN is successful, the associated ^XTMP("DG53970P") entry is removed. 2. If the DFN in the PID segment is not found in ^XTMP("DG53970P") global, the ORU-Z10 message is processed normally. 3. A post-install routine is run that submits the background task IVM*2.0*174 STATUS UPDATE JOB that produces a MailMan message that lists the patient records and associated dependent records from the ^XTMP("DG53970P") global. If there are entries in the ^XTMP("DG53970P") global, this job is submitted to run again in 2 days. The MailMan message lists the following information: a. The total number of patient records and associated dependent records that need to have the SSN field updated. b. Each DFN and the associated dependent IENs in the ^XTMP("DG53970P") that need to have the SSN updated. If an ORU-Z10 message failed to update an SSN for a dependent record, the error is shown with the record. An example of the MailMan message is shown below. Example: Post-Install MailMan Message ------------------------------------- Subj: IVM*2.0*174-#500-VHA/ES CLEANUP OF SSNs IN (#408.13) FILE From: <POSTMASTER> In 'IN' basket. Page 1 ------------------------------------------------------------------------- The job completed to check if patient records still exist in the ^XTMP("DG53970P" global and require a push of corrected SSN data from ES via an HL7(ORU-Z10) message. Job Results: ------------ Facility Name: ZZALBANY.DOMAIN.EXT Station Number: 500 Total patients (ICN/DFN) with dependents not updated: 6 Total dependent (IENs) not updated: 7 Patient ICN/DFN: 5000000001V324625/7171998 Dependent IENs: 2 Patient ICN/DFN: 5000000105V037465/7171999 Dependent IENs: 1 Patient ICN/DFN: 5000000040V317188/7171864 Dependent IENs: 3 4 Patient ICN/DFN: 5000000077V373245/7171902 Dependent IENs: 5 Patient ICN/DFN: 5000000101V983844/7171926 Dependent IENs: 14 Patient ICN/DFN: 5000000111V198302/7171934 Dependent IENs: 13 Patch Components: ================= Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: N/A New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. Incident: INC1928289 Short Description: <SUBSCRIPT>IX+1^DIE1 ^DGPR(408.13 - Error Seen At Multiple Sites Problem: -------- Critical defect #810016 was logged against Enrollment System (ES) 5.3 build. A new build was created to address the defect. Emergency Release ES 5.3.0.07001 implemented code changes to remove a method and method calls that were removing the SSN from the ZDP segment and setting it to a single "space" character. Dependent Social Security Number (SSN) data at the VistA facilities was corrupted and requires a VistA patch to clean up the database corruption. Upon follow-up with the facilities who reported the original error, additional instances of a slightly different error were being seen after the deployment of the code fix. The expected outcome is that no errors would be seen after the deployment of ES 5.3.0.07001. The error logged in the VistA instances is as follows: $ZE= <SUBSCRIPT>IX^DIE1 ^DGPR(408.13,"BS","") K ^DGPR(408.13,"BS",$E(X,6,9),DA) The error is occurring on the second instance of an inbound financial HL7 transmission (ORU-Z10) for a patient. The root cause was determined to be the data (in this case an empty space) which was filed into the SOCIAL SECURITY NUMBER field (#.09) of the INCOME PERSON file (#408.13). The SSN data in that file was potentially degraded by the initial issue. ES was remediated, the second transmission files the correct data; however, still errors due to the previous value. A third or higher transmission should file without error. Resolution: ----------- The processing of the ORU-Z10 message is modified: 1. If the DFN is found in the global ^XTMP("DG53970P"), which was created by patch DG*5.3*970 to capture the records that need to be corrected, then process only the ZDP segments to retrieve and store the dependent SSNs. No other segments or data are processed. 2. If the SSN update was successful, remove the associated entries from the ^XTMP("DG53970P") global. 3. If the SSN update was not successful, store the error in the ^XTMP("DG53970P") global. Once all facilities have installed this emergency patch IVM*2.0*174 by the Compliance date, ES will be sending ORU-Z10 HL7 messages for all veterans that have dependents that needed the SSN updated during non- peak hours. The post-install routine EP^IVM2174P queues the background task IVM*2.0*174 STATUS UPDATE JOB that gathers the DFNs and IENs that are in the ^XTMP("DG53970P") global. These values are listed in an email sent to FORUM MailMan group [email protected]. Members of this mail group will monitor messages received from facilities and coordinate with ES about retransmission of corrected SSN data from ES via an HL7 (ORU-Z10) message. The members of the mail group consist of developers, Software Quality Assurance (SQA), and Health Product Support. A copy of the mail message will be sent to the installer of patch IVM*2.0*174. If there are still entries in the global, this task will automatically be resubmitted to run in the background in 2 days. Once all dependent records identified in the ^XTMP("DG53970P") global have had the SOCIAL SECURITY NUMBER (#.09) field of the INCOME PERSON file (#408.13) successfully updated, the background job will no longer be automatically queued to check the global and send a status message. Test Sites: ----------- * Erie VA Medical Center * Lebanon, PA (Lebanon VA Medical Center) * VA Western New York Healthcare System Software and Documentation Retrieval Instructions: ---------------------------------------------------- Patches for this installation are combined in the following Host File for distribution: IVM_20_P174.KID. The Host File was created to simplify installation at Veterans Health Administration (VHA) facilities. This file can be obtained from one of the anonymous Secure File Transfer Protocol (SFTP) directories. File Name Contents Retrieval Format --------- -------- ---------------- IVM_20_P174.KID IVM*2.0*174 ASCII EAS*1.0*172 Updated documentation describing the new functionality introduced by this patch is available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www.domain.ext/vdl/ Title File Name SFTP Mode -------------------------------------------------------------------------- Release Notes IVM_2_P174_RN.PDF (binary) Patch Installation: Pre/Post Installation Overview: ------------------------------- The post install process will run routine IVM2174P. This routine queues a background job. Upon completion of the job, a MailMan message is sent to FORUM MailMan group [email protected] and the Patch installer. See an example of the message in the 'Listing of Updates' section above. Use default answers for KIDS load/install questions. Multi-Build: http://code.osehra.org/VistA.git/blob/master/Packages/MultiBuilds/IVM_20_P174.KID Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Enrollment+Application+System/Patches/EAS_1.0_172

Patch Subject: NATIVE DOMAIN STANDARDIZATION Description: ============ This patch will add a new field Coding System multiple to files GMRV VITAL TYPE (#120.51), GMRV VITAL QUALIFIER (#120.52) and GMRV VITAL CATEGORY (#120.53) for the purpose of interoperability. * GMRV VITAL TYPE (#120.51) file shall be updated to include a new field to store LOINC code field from the respective SDO. * GMRV VITAL QUALIFIER (#120.52) file shall be updated to include a new field to store the SNOMED CT code from the respective SDO. *GMRV VITAL CATEGORY (#120.53) file shall be updated to include a new field to store the SNOMED CT code from the respective SDO. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- GMRV VITAL TYPE (#120.51) CODING SYSTEM (#8) New GMRV VITAL QUALIFIER (#120.52) CODING SYSTEM (#2) New GMRV VITAL CATEGORY (#120.53) CODING SYSTEM (#2) New Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- Security Keys Associated: Security Key Name ----------------- Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- Additional Information: N/A New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- N/A Problem: -------- Resolution: ----------- N/A Test Sites: ---------- VA Palo Alto Health Care System, California Bedford Healthcare System, Bedford, Massachusetts New York Harbor Healthcare System, New York Documentation Retrieval Instructions: ------------------------------------ Software and Documentation Retrieval Instructions: ---------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext The documentation will be in the form of Adobe Acrobat files. Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ File Description File Name FTP Mode ---------------------------------------------------------------------- Vitals/Measurements Technical Manual GMRV_5_TM_R1016.PDF Binary Patch Installation: Pre/Post Installation Overview: ------------------------------- Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/General+Medical+Record+-+Vitals/Patches/GMRV_5.0_30

Patch Subject: CAS-RXSU2 NEW LETTER CODE FOR DEA SPECIAL HDLG, IDENTIFIERS Description: ============ This patch has the following enhancements for Clinical Ancillary Services (CAS)-Pharmacy Safety Updates (RxSU) Phase 2: 1. Update DEA SPECIAL HANDLING Field Documentation A new code letter "K" was added to for the DEA, SPECIAL HDLG (#3) in the DRUG file (#50) to document in VistA when providers renew medications for patients that cannot be automatically renewed by the patient via Audiocare. Help text added for this field during PSS DRUG ENTER/EDIT option: "K Not Renewable (by telephone) 2. Manage Lookup List Inactive Entries The following files have added a new field identifier to their data dictionaries to indicate if they are marked as Inactive entries. a. ADMINISTRATION SCHEDULE file (#51.1) the INACTIVE field (#12). b. DRUG TEXT file (#51.7) the INACTIVATION DATE field (#2). Patch Components ================ Files & Fields Associated: File Name (#) Field Name(#) New/Modified/Deleted ------------------------------ ---------------- -------------------- ADMINSTRATION SCHEDULE (#51.1) INACTIVE (#12) Modified DRUG TEXT (#51.7) INACTIVATION DATE (#2) Modified Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- ------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- ------------------- N/A Security Keys Associated: Security Key Name New/Modified/Deleted -------------------- ------------------- N/A Templates Associated: Template Name Type File Name (#) New/Modified/Deleted ------------- ---- ------------- ------------------- N/A New Service Requests (NSRs): ---------------------------- 20151007 Test Sites: =========== St Louis Orlando Documentation Retrieval Instructions: ===================================== Updated documentation describing the new functionality introduced by this patch is available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Hines: domain.ext Salt Lake City: domain.ext Documentation can also be retrieved from the VA Software Documentation Library (VDL) on the Internet at the following address: https://www.domain.ext/vdl. File Description File Name FTP Mode -------------------------------------------------------------------------- Pharmacy Data Management User Manual PSS_1_p218_UM.PDF Binary Patch Installation: =================== Pre Installation Overview -------------------------- N/A Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Pharmacy+Data+Management/Patches/PSS_1.0_218

Patch Subject: MASTER VETERAN INDEX VISTA ENHANCEMENTS - SUPPORT LONG NAMES IN VA MPI Description: ============ NOTE: To prevent legacy systems ending up as Treating Facilities, RG* and MPIF* patches should NOT be installed on legacy systems or the FORUM CLAIMS system (since it is NOT a Veterans Affair Medical Center (VAMC) VistA system). There are NO required builds for patch MPIF*1.0*69. NOTE: Master Patient Index (MPI) 'Support for Long Names in VA MPI' enhancements are being distributed in three VistA namespaces: DG, MPIF and RG. The only build enforced requirement for this set of related patches is that MPIF*1.0*69 be installed before RG*1.0*71. (Do NOT install MPIF*1.0*69 or RG*1.0*71 on legacy sites or on the FORUM CLAIMS system) NOTE: Legacy sites and the FORUM CLAIMS system can install just the DG*5.3*974 patch. MPIF*1.0*69 and RG*1.0*71 should NOT be installed on legacy sites or on the FORUM CLAIMS system. The following enhancement exported in this patch was needed to support the collection of the patient's legal name in the Veteran Affairs (VA) Master Person Index, which requires MPI to support storing patient names and aliases greater than the VistA maximum of 30 characters in length. Enhancement MPI as of patch MPI*1.0*125 will start supporting the collection of an individual's legal name, which can now exceed VistA's limitation of a maximum length of 30 characters on the name and/or alias fields. To support this change on the MPI, VistA has been modified with the following change so that it will NOT outright reject the value for exceeding the 30-character maximum length: Created a new Remote Procedure Call (RPC) [MPIF UPDATE NAME COMP FLAG] that will allow MPI to remotely retrieve and update the new Name Components flag stored in the MPI ICN BUILD MANAGEMENT (#984.8) file, LAST PATIENT BUILT field (#3). This field value will be stored in the new file entry identified as 'THREE' (NAME .01) and will control how names passed in the Health Level Seven (HL7) Admit Discharge Transfer (ADT) A31 (Update Person) messages are processed. - NEW Name Components Flag is set to 0 or Null: The component parts of the name in the HL7 message are used to build a name, possibly shortened to 30 characters and filed into the PATIENT (#2) file NAME (#.01) field. The same process is true for aliases in that the component parts of any aliases are used to build the alias, possibly shortened to 30 characters and filed into the ALIAS (#1) multiple NAME (#.01) field in the PATIENT (#2) file. Note: The existing ANAM01 MUMPS cross-reference (X-REF) on the NAME (#.01) field and the ANAM201 X-REF on the ALIAS (#1) multiple NAME (#.01) field on the PATIENT (#2) file will continue to update the corresponding NAME COMPONENTS (#20) entry with the name components passed in the ADT-A31 Person Update HL7 message. - NEW Name Components Flag is set to 1: The component parts of the name or alias in the HL7 message are filed directly into the NAME COMPONENTS (#20) file. Note: The existing ANAME MUMPS X-REF on the fields in the NAME COMPONENTS (#20) file will continue to update the source field [NAME (#.01) field or ALIAS (#1) multiple NAME (#.01) field in the PATIENT (#2) file] with the formatted name. Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------------- -------------------- MPIF UPDATE NAME COMP FLAG NEW Parameter Definitions Associated: Parameter Name New/Modified/Deleted --------------------------- -------------------- N/A Additional Information: New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A Defect Tracking System Ticket(s) & Overview ------------------------------------------- N/A Test Sites: ---------- Birmingham VAMC Salt Lake City HCS Patch Installation: Pre/Post Installation Overview ------------------------------ There are no Pre/Post installation routine processes. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Master+Patient+Index+VistA/Patches/MPIF_1.0_69

Patch Subject: REDESIGN AND UPDATE TO INSTRUMENT SCORING AND MINOR BUG FIXES Description: ============ The primary purpose of this patch is to move instruments previously scored in the YS_MHA_AUX DLL to VistA. The scoring changes result in MHA (Mental Health Assistant) scores being reported in Reminder Dialogs and the Health Summary for these instruments properly. The following instruments are now scored in VistA: Alcohol Use Disorders Identification Test Consumption AUDC Beck Anxiety Inventory BAI Brief Addiction Monitor - Consumption Items BAM-C Brief Addiction Monitor - Revised BAM-R Behavior and Symptom Identification Scale - 24 BASIS-24 Beck Depression Inventory--Second Edition BDI2 Beck Hopelessness Scale BHS Beck Scale for Suicide Ideation (previous short name: BSI) BSS Clinical Dementia Rating CDR Functional Assessment Staging FAST Internalized Stigma of Mental Illness Inventory ISMI Mini-Cog MINICOG NEO Personality Inventory-3 NEO-PI-3 Minnesota Multiphasic Personality Inventory-2-Restructured Form MMPI-2-RF Primary Care PTSD Screen PC PTSD Patient Health Questionnaire-2 PHQ-2 Pain Outcomes Questionnaire POQ Quality of Life Inventory QOLI Short Test of Mental Status STMS Veterans RAND 12 Item Health Survey VR-12 World Health Organization Disability Assessment Schedule 2.0 WHODAS 2 West Haven-Yale Multidimensional Pain Inventory WHYMPI Additionally, the scoring algorithm was changed so that every instrument score is persistently stored in the MH RESULTS File (#601.92). Should an instrument need to be rescored for any reason, there has been functionality added to retain previous scores. The Brief Addiction Monitor (BAM) has been retired. The BAM-R and BAM-IOP should be used instead. The BSI was renamed to the BSS. Scoring the instrument was also modified. Prior to this patch all questions were included in the score, now only questions 1-19 are included in the scoring so the maximum score for the instrument is 38. The current scoring rule stipulates that if more than 5 questions are not answered the instrument would not be scored has been removed. The instrument will now be scored regardless of how many questions are skipped. Skip logic has been added so that if the response to Question 20 is "I have never attempted suicide" (0), question 21 is not asked. The categories of risk have been removed from the report and the following text has been added: The BSS is intended to assess thoughts, plans and intent to die by suicide or attempt suicide over the past week. Total scores can range from 0-38. There is no specific cut-off score to classify severity or guide patient management, however, increasing scores reflect greater risk, and any positive response to any item may reflect the presence of suicidal intention and should be investigated further. The VR-12, question 7 had incorrect responses. The responses prior to the modification were: 1. All of the time 3. A good bit of the time 5. A little of the time 2. Most of the time 4. Some of the time 6. None of the time The correct responses are: 1. All of the time 3. Some of the time 5. None of the time 2. Most of the time 4. A little of the time The responses have been changed to the correct responses. Any previously administered instrument will have response #3 (A good bit of the time) mapped to response #2 (Most of the time) during the patch install. Additionally, the scoring algorithm for the VR-12 was modified to consider skipped questions in the administration. The Beck Depression Inventory--Second Edition (BDI2) results review has been changed. If the response to Item 9 (SUICIDAL THOUGHTS OR WISHES) is 1, 2, or 3 the following statement is added to the report after score: Responses consistent with the presence of suicidal ideation were endorsed in positive direction (item-9), additional clinical assessment is indicated. The Brief Addiction Monitor - Revised (BAM-R) was revised to correct a scoring error. Prior to this patch question 17 was included in the Protective Factors Scale score rather than question 16 resulting in an incorrect scale score. Question 16 is now used in the calculation. The NEO Personality Inventory-3 (NEO-PI-3) Instrument Results Review was modified to display messages when it appears that the respondent answered the items in a random fashion resulting in an invalid administration. The West Haven-Yale Multidimensional Pain Inventory (WHYMPI) was revised to correct a scoring error. The Affective Distress Scale did not properly reverse-score the response to question 6 prior to calculating the score and has been corrected. The Patient Health Questionnaire-2 (PHQ-2) Instrument Results Review was modified. The statement that explains if the screening score indicates a positive or negative result was changed. Additionally, the 2 questions were made required. Currently an example statement is: A score of 4 or more indicates a positive screen. The statement has been changed to: The score on this administration is 4, which indicates a positive screen on the Depression Scale over the past two weeks. Globally for any instrument with skip logic: the skip logic did not work correctly when an instrument was administered using the "One question at a time" function in the Instrument Administrator. If the next to last question should be skipped, MHA did not automatically move to the last question, rather it required the user to click on the 'Next Question' button. Modifications were made so that the user is prompted for the last question. Instruments that have a 'checklist' box question such as the Suicide Behavior Report did not display the last choice in the list box. While a user could select the item, arrow keys had to be used to see the item although it was not intuitive to do so. Modifications were made so that all items are visible in a left justified list. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Mod/Del ------------------ ------------------- ----------- MH TESTS AND SURVEYS (#601.71) Scoring Revision (#93) New Field MH ADMINISTRATIONS (#601.84) Scoring Revision (#14) New Field MH RESULTS (#601.92) Revision History (#11) New Field (Multiple-601.921) New Revision Date (#.01) New Scoring Revision (#2) New Prior Raw Score (#3) New Prior Transformed Score 1 (#4) New Prior Transformed Score 2 (#5) New Prior Transformed Score 3 (#6) New Forms Associated: N/A Mail Groups Associated: N/A Options Associated: Option Name Type New/Mod/Del ----------- ---- ----------- YS BROKER1 version 1.0.3.75~1.0.5.6~1.0.3.75 broker Modified [YS BROKER1] YS*5.01*123 Re-scoring Monitor run routine New [YS123 RESCORING MONITOR] Protocols Associated: N/A Remote Procedures Associated: Remote Procedure Name New/Mod/Del --------------------- ----------- YTQ GET RESULTS New YTQ GET SCRATCH SCORES New Security Keys Associated: N/A Templates Associated: N/A New Service Requests (NSRs): ---------------------------- NSR #20150509: Posttraumatic Stress Disorder (PTSD) Checklist 5 (PCL-5) and Mental Health Assistant Stabilization (MHAS). Patient Safety Issues (PSIs): ----------------------------- PSPO 2497: Mental health instruments that use a complex scoring algorithm display an incorrect score when used in Health Summary and Clinical Reminders. NSD Ticket(s) & Overview: ------------------------- I16022669FY17: If multiple instruments are selected and administered from tabs and a progress note is generated, the Line "URGENCY" is repeated for each instrument, displaying multiple times in one note. Modifications were made so that URGENCY is only displayed once. I17997095FY18: Modifications made to the BSS, see description above. I99044951Y16: There is an error when generating a report for an instrument from the legacy score file for an administration that doesn't exist. Modifications were made to YTQAPI8 to check for this condition and not run the report preventing the error. Test Sites: ---------- Milwaukee Orlando Documentation Retrieval Instructions: ------------------------------------- Documentation can also be found on the VA Software Documentation Library at: http://www.domain.ext/vdl/ MHA3 Installation Guide (YS*5.01*123) YS_501_123_IG.pdf MHA3 Technical Manual and Security Guide YS_MHA_TM.pdf MHA3 User Manual YS_MHA_UM.pdf Software and Documentation Retrieval Instructions: ---------------------------------------------------- This patch is being distributed as a host file. The name of the host file is YS_501_123.KID. This file should be downloaded in ASCII format. The preferred method is to retrieve files from: download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and install guide directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Hines: domain.ext Salt Lake City: domain.ext The Install Guide is also available on the above servers. It is available as .PDF format. This file should be downloaded in BINARY format. File Name: Description: Protocol ========== ============ ========= YS_501_123_IG.pdf MHA3 Patch 123 Install Guide BINARY YS_501_123.KID PATCH 123 Update Host File ASCII YS_501_123.ZIP PATCH 123 MHA GUI V 1.0.3.73 BINARY YS_MHA_TM.PDF MHA3 Technical Manual BINARY YS_MHA_UM.PDF MHA3 User Manual BINARY Documentation can also be found on the VA Software Documentation Library at: http://www.domain.ext/vdl/ Patch Installation ================== Pre-installation Overview: -------------------------- In the past, not all mental health instruments had scores recorded in the MH RESULTS file (#601.92). This patch corrects that by starting a job in the background that will re-score any instruments that do not have properly recorded scores. IMPORTANT NOTE: This will cause the number of records stored in the MH RESULTS file (#601.92) to increase by about 25%. Prior to installing the patch, be sure there is enough space for the ^YTT global to grow. At test sites, the ^YTT global grew by about 3%. See YS_501_123_IG.pdf for more information. Installation: ------------- This patch can be loaded with users on the system. Installation will take five minutes. Refer to the Install Guide, YS_501_123_IG.pdf for complete details. 1. Use the "Load a Distribution" option on the KIDS installation menu. When prompted to enter a host file, type in YS_501_123.KID 2. On the KIDS menu under the 'INSTALLATION' menu, use the following options, as desired: Print Transport Global Compare Transport Global to Current System Verify checksums in Transport Global Backup a Transport Global 3. On the KIDS menu under the 'INSTALLATION' menu, use the following option to install the patch: Install Package(s) When prompted for INSTALL NAME, use YS*5.01*123 4. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//' enter No. 5. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//' enter NO. 6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//' enter NO. Back-Out Plan ------------- For information about back out steps see this document: YS_501_123_IG.pdf in the VistA Documentation Library at: http://www.domain.ext/vdl/ Routine Information: ==================== The second line of each of these routines now looks like: ;;5.01;MENTAL HEALTH;**[Patch List]**;Dec 30, 1994;Build 73 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: YS123PST Before: n/a After: B24739441 **123** Routine Name: YTQAPI11 Before: B25396570 After: B30048720 **85,96,123** Routine Name: YTQAPI2 Before: B24402405 After: B31600888 **85,96,119,121,123** Routine Name: YTQAPI2A Before: B22322420 After: B14847821 **121,134,123** Routine Name: YTQAPI8 Before: B33168164 After: B47316797 **85,121,123** Routine Name: YTQCONS Before: B22590519 After: B21604190 **103,123** Routine Name: YTQPXRM8 Before: B15837966 After: B54326910 **98,123** Routine Name: YTQTIU Before: B22339305 After: B22796222 **85,96,123** Routine Name: YTSAUDTC Before: n/a After: B4359299 **123** Routine Name: YTSBAI Before: n/a After: B10297958 **123** Routine Name: YTSBAMC Before: n/a After: B2786313 **123** Routine Name: YTSBAMR Before: n/a After: B21293411 **123** Routine Name: YTSBAS24 Before: n/a After: B51609198 **123** Routine Name: YTSBDI2 Before: n/a After: B13999964 **123** Routine Name: YTSBHS Before: n/a After: B16408480 **123** Routine Name: YTSBSS Before: n/a After: B9412524 **123** Routine Name: YTSCDR Before: n/a After: B15820283 **123** Routine Name: YTSCORE Before: B5317 After: B54651706 **119,123** Routine Name: YTSCOREV Before: n/a After: B57147321 **119,123** Routine Name: YTSFAST Before: n/a After: B5556501 **123** Routine Name: YTSISMI Before: n/a After: B13349648 **123** Routine Name: YTSMINIC Before: n/a After: B7002619 **123** Routine Name: YTSMPI2 Before: n/a After: B33844449 **123** Routine Name: YTSMPI2E Before: n/a After: B27428150 **123** Routine Name: YTSMPI2H Before: n/a After: B30811677 **123** Routine Name: YTSMPI2P Before: n/a After: B8572910 **123** Routine Name: YTSMPI2S Before: n/a After: B34423692 **123** Routine Name: YTSMPI2T Before: n/a After: B46267603 **123** Routine Name: YTSMPI2U Before: n/a After: B72823730 **123** Routine Name: YTSMPI2V Before: n/a After: B23775047 **123** Routine Name: YTSMPI2Y Before: n/a After: B14501308 **123** Routine Name: YTSMPIR Before: n/a After: B25492700 **123** Routine Name: YTSMPIRD Before: n/a After: B38704344 **123** Routine Name: YTSNEOP1 Before: n/a After: B60236597 **123** Routine Name: YTSNEOP2 Before: n/a After: B59142535 **123** Routine Name: YTSNEOP3 Before: n/a After: B87270089 **123** Routine Name: YTSNEOPI Before: n/a After: B37891902 **123** Routine Name: YTSPHQ2 Before: n/a After: B5651900 **123** Routine Name: YTSPOQ Before: n/a After: B96628593 **123** Routine Name: YTSPSOCQ Before: n/a After: B5520119 **123** Routine Name: YTSPTSD Before: n/a After: B3936166 **123** Routine Name: YTSQOLI Before: n/a After: B63479643 **123** Routine Name: YTSQOLI1 Before: n/a After: B44866396 **123** Routine Name: YTSSTMS Before: n/a After: B5369687 **123** Routine Name: YTSVR12 Before: n/a After: B33765075 **123** Routine Name: YTSVRM1 Before: n/a After:B101904148 **123** Routine Name: YTSVRM10 Before: n/a After:B110202549 **123** Routine Name: YTSVRM11 Before: n/a After:B110768739 **123** Routine Name: YTSVRM12 Before: n/a After:B111319692 **123** Routine Name: YTSVRM13 Before: n/a After:B110704605 **123** Routine Name: YTSVRM14 Before: n/a After:B112180326 **123** Routine Name: YTSVRM15 Before: n/a After:B113311749 **123** Routine Name: YTSVRM16 Before: n/a After:B105471044 **123** Routine Name: YTSVRM17 Before: n/a After:B104286520 **123** Routine Name: YTSVRM18 Before: n/a After:B108834336 **123** Routine Name: YTSVRM19 Before: n/a After:B112232029 **123** Routine Name: YTSVRM2 Before: n/a After:B107395949 **123** Routine Name: YTSVRM20 Before: n/a After:B109477746 **123** Routine Name: YTSVRM21 Before: n/a After:B113718493 **123** Routine Name: YTSVRM22 Before: n/a After:B112802373 **123** Routine Name: YTSVRM23 Before: n/a After:B112451696 **123** Routine Name: YTSVRM24 Before: n/a After:B111885516 **123** Routine Name: YTSVRM25 Before: n/a After:B112133328 **123** Routine Name: YTSVRM26 Before: n/a After:B116453086 **123** Routine Name: YTSVRM27 Before: n/a After:B103131418 **123** Routine Name: YTSVRM28 Before: n/a After:B107257258 **123** Routine Name: YTSVRM29 Before: n/a After: B59488015 **123** Routine Name: YTSVRM3 Before: n/a After:B107344511 **123** Routine Name: YTSVRM4 Before: n/a After:B110421934 **123** Routine Name: YTSVRM5 Before: n/a After:B109737134 **123** Routine Name: YTSVRM6 Before: n/a After:B109448573 **123** Routine Name: YTSVRM7 Before: n/a After:B109520267 **123** Routine Name: YTSVRM8 Before: n/a After:B114246719 **123** Routine Name: YTSVRM9 Before: n/a After:B109292953 **123** Routine Name: YTSVRP1 Before: n/a After:B108937936 **123** Routine Name: YTSVRP10 Before: n/a After:B109710265 **123** Routine Name: YTSVRP11 Before: n/a After:B110441274 **123** Routine Name: YTSVRP12 Before: n/a After:B115737130 **123** Routine Name: YTSVRP13 Before: n/a After:B112120292 **123** Routine Name: YTSVRP14 Before: n/a After:B114239947 **123** Routine Name: YTSVRP15 Before: n/a After:B114967433 **123** Routine Name: YTSVRP16 Before: n/a After:B112965310 **123** Routine Name: YTSVRP17 Before: n/a After:B110119447 **123** Routine Name: YTSVRP18 Before: n/a After:B110264488 **123** Routine Name: YTSVRP19 Before: n/a After:B112080883 **123** Routine Name: YTSVRP2 Before: n/a After:B109914546 **123** Routine Name: YTSVRP20 Before: n/a After:B108221298 **123** Routine Name: YTSVRP21 Before: n/a After:B113315435 **123** Routine Name: YTSVRP22 Before: n/a After:B112678239 **123** Routine Name: YTSVRP23 Before: n/a After:B118576259 **123** Routine Name: YTSVRP24 Before: n/a After:B110767524 **123** Routine Name: YTSVRP25 Before: n/a After:B112405922 **123** Routine Name: YTSVRP26 Before: n/a After:B113560290 **123** Routine Name: YTSVRP27 Before: n/a After:B111923844 **123** Routine Name: YTSVRP28 Before: n/a After:B100192560 **123** Routine Name: YTSVRP29 Before: n/a After:B119686539 **123** Routine Name: YTSVRP3 Before: n/a After:B110444755 **123** Routine Name: YTSVRP4 Before: n/a After:B110721614 **123** Routine Name: YTSVRP5 Before: n/a After:B111595130 **123** Routine Name: YTSVRP6 Before: n/a After:B110639774 **123** Routine Name: YTSVRP7 Before: n/a After:B111208936 **123** Routine Name: YTSVRP8 Before: n/a After:B113389193 **123** Routine Name: YTSVRP9 Before: n/a After:B107850960 **123** Routine Name: YTSWHODA Before: n/a After: B73599481 **123** Routine Name: YTSWHYMP Before: n/a After: B49407784 **123** Routine Name: YTXCHG Before: B53596106 After: B65891565 **121,123** Routine Name: YTXCHGM Before: B68668785 After: B69364359 **121,123** Routine Name: YTXCHGT Before: B19049216 After: B22991016 **121,123** Routine Name: YTXCHGU Before: B33209921 After: B38521815 **121,123** Routine list of preceding patches: 98, 103, 134 ============================================================================= User Information: Entered By : Date Entered : JAN 05, 2016 Completed By: Date Completed: FEB 28, 2019 Released By : Date Released : MAR 05, 2019 ============================================================================= Packman Mail Message: ===================== $END TXT Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Mental+Health/Patches/YS_5.01_123

Patch Subject: MENTAL HEALTH ASSISTANT SCL9R MISSING ANSWER CHOICES Description: ============ The patch addresses one (1) issue: 1. When using the SCL9R instrument in the Mental Health Assistant, only four (4) answer choices are offered when there should be five (5). Associated NSR(s): ------------------ N/A Associated Remedy ticket(s): ========================== 1. INC3526338 - SCL9R Missing Answer Choices Associated NSR(s): ================== N/A Participating Test Sites: ========================= Boise VA Medical Center, ID VA Illiana Health Care System (Danville, IL) Ticket Overview: ================ 1. INC3526338 - SCL9R Missing Answer Choices Problem: -------- When using the SCL9R instrument in the Mental Health Assistant, only four (4) answer choices are offered when there should be five (5). This occurs because of an incorrect entry in the MH CHOICETYPES (#601.751) file. Specifically, the CHOICETYPE ID `1272 has a SEQUENCE (#1) field value of 5 (should be 1) and a CHOICE ID (#2) field value of "Extremely" (should be "Not at all"). Resolution: ----------- Post install routine YS143PIR corrects the field values and resets the LAST EDIT DATE (#18) field for the SCL9R instrument in the MH TESTS AND SURVEYS (#601.71) file to force the Mental Health Assistant GUI to reload the survey with the corrected answers. Components: =========== N/A Software and Documentation Retrieval Instructions: ================================================== No documentation associated with this patch other than this patch description. This patch is being distributed as a Packman message. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Mental+Health/Patches/YS_5.01_143

Patch Subject: BACKGROUND PROCESSOR (BP) DEFECT FIXES Description: ============ Associated Patches: =================== This patch must be installed after MAG*3.0*198. Subject: BACKGROUND PROCESSOR (BP) DEFECT FIXES ======== Category: OTHER ========= Description: ============= This document describes MAG*3.0*214, a patch that provides fixes to the Background Processor (BP). This patch addresses the following issues: Imaging Site Parameters screen, system displays an error message "Value is not initialized". BP Queue processor is stopping with an error at some sites. After installing the MAG*3.0*196, some background processor sites are getting prompted for 2-factor authentication when starting the application. Network Password Update on BGP causing issues. Resolved issue of the Event Log displaying incorrect patch. Patch Components: ================= This patch includes software and documentation files. This document, MAG3_0P 214_Patch_Description.pdf, provides an overview, explains the changes, and outlines the installation for this patch. MAG3_0P214_README.txt, if present, is an informative file associated with the patch released. Software & Documentation: ========================= File Name Description ========== =========== MAG3_0P214.KID Kernel Installation and Distribution System(KIDS)build for Patch 214 MAG3_0P214_Background_Processor_Setup.exe Background Processor client installation file. MAG3_0P214_Patch_Description.pdf Patch Description for P214 Mag_BP_User_Manual.pdf Background Processor User Manual Files & Fields Associated: ========================== There are no files or fields associated with this patch. Forms Associated: ================= There are no forms associated with this patch. Mail Groups Associated: ======================= There are no mail groups associated with this patch. Options Associated: =================== There are no options associated with this patch. Protocols Associated: ===================== There are no protocols associated with this patch. Security Keys Associated: ========================= There are no security keys associated with this patch. Templates Associated: ===================== There are no templates associated with this patch. Additional Information: ======================= New Service Requests (NSRs): ============================ There are no new service requests addressed in this patch. Patient Safety Issues (PSIs): ============================= There are no patient safety issues associated with this patch. Defect Tracking System Ticket(s) & Overview =========================================== 1. Defect 740851 (Trouble Ticket # INC0300885)-Imaging Site Parameters screen, system displays an error message "Value is not initialized". Problem: ======== Issue 1: ======== When user opens Background Processor - Imaging Site Parameters screen, system displays an error message "Value is not initialized" and Background Processor freezes. The user cannot proceed forward. Issue 2: ======== Users are experiencing an issue where they cannot save the Default User Preference when selecting a different name from was previous selected. Resolution: ========== A new Remote Procedure Call (RPC) "MAGQBP VAL" is called before the Imaging Site Parameters window is opened. This new RPC will validate the current values of the pointer fields: #100 DEFAULT USER PREFERENCE #.03 IMAGE NETWORK WRITE LOCATION #2.01 JUKEBOX WRITE LOCATION #1.02 PACS DIRECTORY #1.03 PACS IMAGE WRITE LOCATION A message window will be displayed to the user if any of the current values are invalid. If the current value of the Default User Preferences field is invalid, it will be deleted from the IMAGING SITE PARAMETERS File (#2006.1). If invalid data is found, a confirmation message will be displayed to the user. Click OK and the Site Parameters window will open. Note: If the Site Parameters window does not open, an authorized person will need to correct the invalid pointer in VistA using Fileman Enter/Edit. 2. Defect 741310 (Trouble Tickets # INC0298707, INC0586047)-BP Queue processor is stopping with an error at some sites. Problem: ======== When running the Jukebox Queue and MAG*3.0*196 is running for a while, unexpectedly the user will get stuck into an RPC Exception loop. The users are prompted for access and verify code. Resolution: =========== Occasionally, when an RPC Exception occurs, the connection to VistA is lost. When the connection is lost, the BP will try to silently re-connect to VistA without user input. In this issue, the user is prompted for their Access and Verify Codes because the user context has been cleared. The code has been modified to correctly use the last user context for the silent re-connect to VistA. 3. Defect 741968 (Trouble Ticket # INC0383466)- 2-Factor Authentication prompt appearing for some users. Problem: ======== After installing the MAG*3.0*196, when launching the BP Queue Processor, some sites are getting prompted for 2-factor authentication. The users launch the BP Queue Processor then will receive the 2 - Factor Authentication message. If the user clicks cancel, the BP Queue Processor will launch the window for access/verify code. The 2 - Factor Authentication should not appear at all. Some users are using Dameware to remote login to the server and login into the server using the administration password. Resolution: =========== MAG*3.0*196 and newer versions of the BP use the Broker Development Kit (BDK) version 65 to connect to VistA. BDK 65 incorporates 2FA authentication to login to VistA. The BP code has been modified to use the login functionality from the last version of the BDK that did not incorporate 2FA authentication. 4. Defect 744739 (Ticket # R16489435FY17) - Network Password Update on BGP causing issues. Problem: ======== When the user updates the Network Password in the Background Processor, the system would randomly add an extra space to the end of the encrypted password stored in VistA, which causes the user issues when trying to log into other areas of VistA Imaging. Resolution: =========== The BP uses Kernel functions to generate encrypted passwords. If spaces exist in the encrypted password, the BP will continually re-encrypt the password until no spaces exist. The user may see an information window that says the password will be re-encrypted. But there is no action required on the user's part, except clicking 'OK'. 5. Defect 806306: BP Event Log Issue Problem: ======== In the Event Log, of the BP Main Window, the value for 'Vista Imaging Install' incorrectly displays 3.0p196. Resolution: =========== The Event Log was fixed to correctly display the latest installed BP Patch (MAG*3.0*214). Test Sites: =========== The following sites are test sites for this patch: Oscar G. Johnson VAMC (Iron Mountain) Phoenix VA Healthcare System Syracuse VAMC (VISN2-Upstate NY) Software and Documentation Retrieval Instructions: ================================================== Software being released and/or documentation describing the new functionality introduced by this patch are available. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Location Site ======== ==== Hines domain.ext Salt Lake City domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/. Patch Installation: =================== Supported Client Versions ========================= When MAG*3.0*214 is released, the list of supported versions of Background Processor will change: Supported Versions No Longer Supported ================== =================== 3.0.214 3.0.198 3.0.196 3.0.135 Note: When a user enters invalid Access/Verify Codes while logging into VistA, the system gives them an error message. In patch 214, the Error message is hidden under the main Vista Sign-on window. The user has to move the VistA Sign-on window, then click 'OK' in the Error message window to be able to continue. A fix for this issue is scheduled for a future Background Processor patch. Pre/Post Installation Overview: =============================== MAG*3.0*214 KIDS must be installed on the VistA System prior to running the new executables. This patch must be installed by the compliance date. All sites running VistA Imaging 3.0 must install the KIDS portion of this patch. This patch may be loaded while the VistA Imaging System is active. Installation will take less than one minute. Important: Any Background Processor applications that are running must be stopped and closed prior to the installation of the KIDS and Client software. Any image capture application (Clinical Capture and DICOM Gateway processing) can continue to run during the installation. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Imaging/Patches/MAG_3.0_214

Patch Subject: SHRPE ENHANCEMENTS FOR PATIENT RECORD FLAGS Description: ============ NOTE: This patch is requested to be installed prior to or on the compliance date, which is 3 days after its release. Patient Record Flags (PRF) data can get out of sync when some sites have installed the patch and some have not and this can potentially cause patient safety issues. The patch description provides instructions on how to fix the issues if they arise. While the shorter period of installation cannot guarantee there will be no issues, this approach can minimize the risk by reducing the chance of out-of-sync occurrences and in the case it does happen, there will be fewer sites that will need to fix issues manually. This patch addresses enhancements to Patient Record Flags (PRF) to improve the delivery of targeted Mental Health care for individuals at high risk for suicide. Enhancements to PRF reports were made to improve effective management of coordination of care for high risk individuals and to include new data elements introduced with this patch. 1. The Disruptive Behavior Reporting System (DBRS) record numbers are now recorded in the PRF FileMan files to enable a convenient reference between VistA and DBRS. The patch contains the following modifications to support DBRS functionality: a) Ability to enter/edit multiple DBRS data sets on National Category 1 Behavioral PRF flags in VistA. b) Enforced format of DBRS Number field to be consistent with DBRS case numbers in DBRS system. c) HL7 updates to pertinent messages to include DBRS data set information. d) Implemented business rules around editing DBRS data sets and tracking the author for enforcement of editing rules. e) New DBRS Historical Report to display historical edits made to a single National Category 1 Behavioral PRF flag in VistA. f) New Application Programming Interface (API) GETDBRS^DGPFDBRS was added to the Registration (DG) application to provide access to DBRS data to external applications like Computerized Patient Record System (CPRS) for displaying DBRS data on the screen. The Integration Control Registration (ICR)# 6874 was introduced for this new interface. 2. Modification to support Text Integration Utility (TIU)/CPRS Progress Note Properties' flag action list functionality. The new array element "ORIG FAC" was added to the output of the pre-existing API $$GETHTIU^DGPFAPI1. The new data element contains the facility that created the Assignment History record. This will allow the TIU application to retrieve the data via RPC TIU GET PRF ACTIONS and display the originating facility on the Progress Note Properties' flag action list and sort entries by these values. Note: The respective TIU modification is required to make this functionality available for users and it will be included in the future version of CPRS. The ICR# 4383, that covers $$GETHTIU^DGPFAPI1, was updated accordingly. 3. Enhancements to PRF flags ownership transfers. The patch implements new functionality and makes modifications to existing code to improve the process of ownership transfer and eliminate issues reported by PRF users: a) The new ListMan action "PRF Owner Transfer Request" (FT) in the Record Flag Assignment [DGPF RECORD FLAG ASSIGNMENT] menu option was created to request ownership transfer of PRF assignments. - When a user requests ownership transfer, the division that was used to sign into VistA will be the new owner. Note: This modification addresses PRF transfer issues experienced by integrated sites. - If the assignment is active, a MailMan message will be sent to the current owner's mail group requesting approval. - If the assignment is inactive, the transfer will be done immediately and a MailMan message will be sent notifying the current owner of the change of ownership action. - The functionality prevents duplicate requests. b) The corresponding new menu option Record Flag Transfer Requests (TR) was created to manage ownership transfer requests: The new menu option allows users to: - list requests and their statuses - review request details - approve or reject requests - enter a reason for transfer request and a reason for approval/rejection c) The MailMan modification is sent to PRF mail group 'DGPF PRF TRANSFER REQUESTS' when PRF ownership request is - sent - received - approved - rejected d) Both the Change Assignment Ownership (CO) and the PRF Owner Transfer Request (FT) actions will set the Review Date on the new owner's system to the default value for that flag. e) Change Assignment Ownership (CO) action is blocked from transferring an Active PRF assignment if an existing request created in PRF Owner Transfer Request (FT) action is pending. f) New option, DGPF RECORD REFRESH is sent out as a stand alone OPTION not attached to any menu. It is locked with the SECURITY KEY "DGPF TRANSMISSIONS". This option was designed to be used by VA Tier II Support or at their direction. This action allows the user to retransmit the entire PRF record to other sites to enforce PRF flag synchronization across the sites where the patient is registered. 4. Various enhancements and fixes related to PRF flag HL7 transmissions: a) In the Assign Flag (AF) and the Edit Flag Assignment (EF) actions, the two word processing fields for Assignment Narrative and Edit Reason will require a minimum of three consecutive alpha characters. b) HL7 messages for PRF related transmission and their processing were updated to use external names of PRF flag instead of internal entry numbers (IENs). c) PRF HL7 message processing code was updated to properly handle HL7 delimiters entered by users in free text fields. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name(Number) New/Modified/Deleted ---------------------------- -------------------- ------------------- PRF ASSIGNMENT FILE (#26.13) DBRS NUMBER (#2) New Multiple DBRS NUMBER (#26.131) DBRS NUMBER (#.01) New OTHER DBRS DATA (#.02) New DATE (#.03) New CREATE SITE (#.04) New PRF ASSIGNMENT HISTORY (#26.14) PRF ASSIGNMENT (#.01) Modified ACTION (#.03) Modified CREATED BY SITE (#.09) New DBRS NUMBER (#2) New Multiple DBRS NUMBER (#26.142) DBRS NUMBER (#.01) New DBRS OTHER (#.02) New DATE (#.03) New STATUS (#.04) New CREATE SITE (#.05) New PRF HL7 REQUEST LOG (#26.22) New Bulletins Associated: New/Modified/ Bulletin Name Deleted ------------- ------------- N/A Dialogs Associated: New/Modified/ Dialog Name Deleted ----------- ------------- N/A Forms Associated: New/Modified/ Form Name File Name (Number) Deleted --------- ------------------ ------------- N/A Functions Associated: New/Modified/ Function Name Deleted ------------- ------------- N/A HL Logical Link: New/Modified/ HL Logical Name Deleted --------------- ------------- N/A HL7 Application Parameters: New/Modified/ HL7 Parameter Name Deleted ------------------ ------------- PRF-TRANS-REQ New PRF-TRANS-RESP New HLO Application Registry: New/Modified/ HLO Registry Name Deleted ----------------- ------------- N/A Help Frames Associated: New/Modified/ Help Frame Name Deleted --------------- ------------- N/A Mail Groups Associated: New/Modified/ Mail Group Name Deleted --------------- ------------- DGPF PRF TRANSFER REQUESTS New Options Associated: New/Modified/ Option Name Type Deleted ----------- ----------- ------------- DGPF DISRUPT BEHAVIOR REPORT Run Routine New DGPF PRF TRANSFER REQUESTS Run Routine New DGPF RECORD FLAG REPORTS MENU Menu Modified DGPF RECORD FLAGS MAIN MENU Menu Modified DGPF RECORD REFRESH Run Routine New Parameter Definitions: New/Modified/ Parameter Name Deleted -------------- ------------- N/A Parameter Template: New/Modified/ Template Name Deleted ------------- ------------- N/A Protocols Associated: New/Modified/ Protocol Name Deleted ------------- ------------- DGPF PRF QBP/Q11 EVENT New DGPF PRF QBP/Q11 SUBSC New DGPF PRF RSP/K11 EVENT New DGPF PRF RSP/K11 SUBSC New DGPF PRF TR REQ CHANGE VIEW New DGPF PRF TR REQ DETAILS New DGPF PRF TR REQ MENU New DGPF PRF TR REQ REVIEW New DGPF RECORD FLAG ASSIGNMENT MENU New DGPF TRANSFER FLAG New VALM QUIT Unchanged Remote Procedures Associated: New/Modified/ Remote Procedure Name Deleted --------------------- ------------- N/A Security Keys Associated: New/Modified/ Security Key Name Deleted ----------------- ------------- N/A Templates, Input Associated: New/Modified/ Template Name Type File Name (Number) Deleted ------------- ---- ------------------ ------------- N/A Templates, List Associated: New/Modified/ Template Name Type Deleted ------------- ---- ------------- DGPF PRF TRANSFER REQUESTS List New Templates, Print Associated: New/Modified/ Template Name Type File Name (Number) Deleted ------------- ---- ------------------ ------------- N/A Templates, Sort Associated: New/Modified/ Template Name Type File Name (Number) Deleted ------------- ---- ------------------ ------------- N/A Additional Information: N/A New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A Remedy Ticket(s) & Overview --------------------------- 1. I17222368FY18 - No Category I Patient Record Flag Assignments found Problem: ------- "No Category I Patient Record Flag Assignments found" is the response for queries made concerning existing Patient Record Flag (PRF) data and no PRF data is transmitted. It has been determined a PRF file entry having a lone associated comment consisting solely of a punctuation/ control character is treated by PRF-HL7 processing as not-valid; and is treated as if there is no flag history. Resolution: ---------- Modify routine DGPFHLUT to transmit an HL7 message when entering a punctuation as a comment and store it with quotes so that it does not interfere with HL7 message format or integrity. Test Sites: ---------- Syracuse West Palm Beach Iowa City Des Moines Omaha Documentation Retrieval Instructions ------------------------------------ The software is released as a PackMan patch message and is distributed via FORUM. Software documentation describing the new functionality introduced by this patch is available for downloading from the ANONYMOUS.SOFTWARE directories or from the VA Software Documentation Library. The preferred method is to retrieve the files from the ANONYMOUS.SOFTWARE directories is from download.vista.domain.ext. This transmits the files from the first available server. Sites may elect to retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www.domain.ext/vdl/ Title File Name SFTP Mode ----------------------------------------------------------------------- PIMS Technical Manual pimstm.pdf Binary Patient Record Flags prfhl7is.pdf Binary HL7 Interface Specification Patient Record Flags patient_record_flags_user_guide.pdf Binary User Guide Patch Installation: Pre/Post Installation Overview ------------------------------ Post-installation routine DG53P951 creates a non-human user "DGPRF,INTERFACE", if one does not already exist. This user account is used for sending various MailMan notifications and ownership transfers of inactive PRF flags. The installer needs to contact the site's Suicide Prevention Coordinators (National Category 1 High Risk for Suicide flags) and Disruptive Behavior Committee Chair (National Category 1 Behavioral flags) to identify the person who will be coordinating transfer requests notifications for PRF flags. That person's name should be entered at the following prompt for the newly created mailgroup: Enter the Coordinator for Mail Group 'DGPF PRF TRANSFER REQUESTS': During installation of the patch, the "HL7 CHECK POST-INSTALLATION" report will be generated and sent to: - the installer, - POSTMASTER, - DGPF BEHAVIORAL FLAG REVIEW mail group, - IRM mail group to identify potential DBRS data synchronization issues. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Registration/Patches/DG_5.3_951

Patch Subject: MASTER VETERAN INDEX VISTA ENHANCEMENTS - SUPPORT LONG NAMES IN VA MPI Description: ============ NOTE: Master Patient Index (MPI) 'Support for Long Names in VA MPI' enhancements are being distributed in three VistA namespaces: DG, MPIF and RG. The only build enforced requirement for this set of related patches is that MPIF*1.0*69 be installed before RG*1.0*71. (Do NOT install MPIF*1.0*69 or RG*1.0*71 on legacy sites or on the FORUM CLAIMS system) NOTE: Legacy sites and the FORUM CLAIMS system can install just the DG*5.3*974 patch. MPIF*1.0*69 and RG*1.0*71 should NOT be installed on legacy sites or on the FORUM CLAIMS system. DG*5.3*578, DG*5.3*837, DG*5.3*937 and DG*5.3*944 are the required builds for patch DG*5.3*974. The following enhancement exported in this patch was needed to support the collection of the patient's legal name in the Veteran Affairs (VA) Master Person Index, which requires MPI to support storing patient names and aliases greater than the VistA maximum of 30 characters in length. Enhancement MPI as of patch MPI*1.0*125 will start supporting the collection of an individual's legal name, which can now exceed VistA's limitation of a maximum length of 30 characters on the name and/or alias fields. To support this change on the MPI, VistA has been modified with the following changes so that it will NOT outright reject the value for exceeding the 30-character maximum length: - Created a new Remote Procedure Call (RPC) [DG UPDATE NAME COMPONENTS] that will allow MPI to remotely retrieve and update the name components stored in the NAME COMPONENTS (#20) file for a patient's name or alias at the site. - Modified the Health Level Seven (HL7) processing code for the Admit Discharge Transfer (ADT) A08 (Update Patient) and A31 (Update Person) HL7 messages received from MPI that determines whether 'Aliases' need to be added or deleted from the PATIENT (#2) file, so that the comparison will now occur against fields in the NAME COMPONENTS (#20) file. - Modified the HL7 Patient Identification (PID) builder so that the 'Alias' name components from the NAME COMPONENTS (#20) file are placed into the PID-5 segment, which will ensure that the Alias components in the HL7 message reflect the true alias component values which will be filed into the Correlation on the MPI. Note: Previously, the 'Alias' components were obtained by parsing the Alias Name (.01) into its component parts. Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------------- -------------------- DG UPDATE NAME COMPONENTS NEW Parameter Definitions Associated: Parameter Name New/Modified/Deleted --------------------------- -------------------- N/A Additional Information: New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A Defect Tracking System Ticket(s) & Overview ------------------------------------------- N/A Test Sites: ---------- Birmingham VAMC Salt Lake City HCS Patch Installation: Pre/Post Installation Overview ------------------------------ There are no Pre/Post installation routine processes. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Registration/Patches/DG_5.3_974

Patch Subject: ANATOMIC PATHOLOGY LOG-IN: SCREEN FOR SEX-SPECIFIC TOPOGRAPHY Description: ============ This patch addresses the following issue: Anatomic Pathology Log-In does not require that the patient's sex must match the SEX SPECIFIC (#2.5) field in the TOPOGRAPHY FIELD (#61) file for specimens (if the sex specific field is defined). Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ -------------------------- -------------------- CYTOPATHOLOGY: SPECIMEN SUB-FIELD SPECIMEN TOPOGRAPHY (#.06) Modified (#63.902) ELECTRON MICROSCOPY: SPECIMEN SUB-FIELD SPECIMEN TOPOGRAPHY (#.06) Modified (#63.202) SURGICAL PATHOLOGY: SPECIMEN SUB-FIELD SPECIMEN TOPOGRAPHY (#.06) Modified (#63.812) Blood Bank Review: ================= EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*514 does not contain any changes to the VISTA BLOOD BANK Software as defined by ProPath standard titled: BBM Team Review of VistA Patches. EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*514 does not alter or modify any software design safeguards or safety critical elements functions. RISK ANALYSIS: Changes made by patch LR*5.2*514 have no adverse effect on Blood Bank software functionality, therefore RISK is none. VALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes made, no specific validation requirements exist as a result of installation of this patch. Defect Tracking System Ticket(s) & Overview: =========================================== 1. INC2906846 - Anatomic Pathology Log-In Sex-Specific Topography Validation Problem: ------- The Log-in, anat path [LRAPLG] option does not require that the patient's sex must match any sex-specific specimen topography specimens. These specimens correspond to an entry from the TOPOGRAPHY FIELD (#61) file that is defined with "F" for "female" or "M" for "male" in the SEX SPECIFIC (#2.5) field. If a specimen is logged in with a sex-specific mismatch, that entry is not accepted during the later steps in Anatomic Pathology Data Entry. Resolution: ---------- Modify the data dictionary input transforms and screens for the Surgical Pathology, Cytopathology, and Electron Microscopy (EM) accession areas with the following requirement: If the SEX SPECIFIC (#2.5) field of the TOPOGRAPHY FIELD (#61) file is defined, the patient's sex must match the field entry. Any entries in the TOPOGRAPHY FIELD (#61) file that have an "M" or "F" entry in the SEX SPECIFIC (#2.5) field will not display to the user as a selection choice if the entry is not the same as the patient's sex. NOTE: This change is not necessary for the Autopsy accession area since specimen topography is not entered during the Log-in, anat path [LRAPLG] option. The change will also not be implemented for Laboratory accession areas not related to Anatomic Pathology. Test Sites: ========== VA Puget Sound HCS Syracuse VAMC Data Dictionaries Before: ======================== 63.902,.06 SPECIMEN TOPOGRAPHY 0;6 POINTER TO TOPOGRAPHY FIELD FILE (#61) LAST EDITED: NOV 25, 2005 DESCRIPTION: This field contains the topography location for this test. 63.202,.06 SPECIMEN TOPOGRAPHY 0;6 POINTER TO TOPOGRAPHY FIELD FILE (#61) LAST EDITED: NOV 25, 2005 DESCRIPTION: This field contains the topography location for this test. 63.812,.06 SPECIMEN TOPOGRAPHY 0;6 POINTER TO TOPOGRAPHY FIELD FILE (#61) LAST EDITED: FEB 08, 2007 DESCRIPTION: This field contains the topography location for this test. Data Dictionaries After: ======================= 63.902,.06 SPECIMEN TOPOGRAPHY 0;6 POINTER TO TOPOGRAPHY FIELD FILE (#61) INPUT TRANSFORM: S DIC("S")="I $P(^LAB(61,+Y,0),U,3) =""""!($P(^LAB(61,+Y,0),U,3)=$G(SEX))" D ^DIC K DIC S DIC=$G(DIE),X=+Y K:Y<0 X LAST EDITED: NOV 30, 2018 HELP-PROMPT: This field contains the topography location for this test. DESCRIPTION: This field contains the topography location for this test. If the SEX SPECIFIC (#2.5) field of the TOPOGRAPHY FIELD (#61) file is defined, the sex of the patient must match. SCREEN: S DIC("S")="I $P(^LAB(61,+Y,0),U,3) =""""!($P(^LAB(61,+Y,0),U,3)=$G(SEX))" EXPLANATION: If this message appears after entering a topography, the entry might be: (1) not on file; (2) misspelled; or (3) the topography has a restriction by sex that does not match the patient's sex. 63.202,.06 SPECIMEN TOPOGRAPHY 0;6 POINTER TO TOPOGRAPHY FIELD FILE (#61) INPUT TRANSFORM: S DIC("S")="I $P(^LAB(61,+Y,0),U,3) =""""!($P(^LAB(61,+Y,0),U,3)=$G(SEX))" D ^DIC K DIC S DIC=$G(DIE),X=+Y K:Y<0 X LAST EDITED: NOV 30, 2018 HELP-PROMPT: This field contains the topography location for this test. DESCRIPTION: This field contains the topography location for this test. If the SEX SPECIFIC (#2.5) field of the TOPOGRAPHY FIELD (#61) file is defined, the sex of the patient must match. SCREEN: S DIC("S")="I $P(^LAB(61,+Y,0),U,3) =""""!($P(^LAB(61,+Y,0),U,3)=$G(SEX))" EXPLANATION: If this message appears after entering a topography, the entry might be: (1) not on file; (2) misspelled; or (3) the topography has a restriction by sex that does not match the patient's sex. 63.812,.06 SPECIMEN TOPOGRAPHY 0;6 POINTER TO TOPOGRAPHY FIELD FILE (#61) INPUT TRANSFORM: S DIC("S")="I $P(^LAB(61,+Y,0),U,3) =""""!($P(^LAB(61,+Y,0),U,3)=$G(SEX))" D ^DIC K DIC S DIC=$G(DIE),X=+Y K:Y<0 X LAST EDITED: NOV 30, 2018 HELP-PROMPT: This field contains the topography location for this test. DESCRIPTION: This field contains the topography location for this test. If the SEX SPECIFIC (#2.5) field of the TOPOGRAPHY FIELD (#61) file is defined, the sex of the patient must match. SCREEN: S DIC("S")="I $P(^LAB(61,+Y,0),U,3) =""""!($P(^LAB(61,+Y,0),U,3)=$G(SEX))" EXPLANATION: If this message appears after entering a topography, the entry might be: (1) not on file; (2) misspelled; or (3) the topography has a restriction by sex that does not match the patient's sex. Patch Installation: Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Lab+Service/Patches/LR_5.2_514

Patch Subject: INCIDENT REPORTING DATA ENTRY DEACTIVATION Description: ============ Incident Reporting patch, QAN*2.0*34, marks menu options as, "Disabled-USE Joint Patient Safety Reporting-JPSR". This was requested by the Veterans Health Administration National Center for Patient Safety Joint Patient Safety Reporting (VHANCPS JPSR) TEAM. Patch Components: ================= Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Group Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: N/A New Service Request (NSRs): --------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. Rational Defect# 781764- Place Incident Reporting Menu Options "out of order". Problem: -------- The VHANCPS JPSR TEAM has identified that several Incident Reporting menu options are obsolete and no longer in use. They have requested the options listed in this patch be disabled with the message: "Disabled-USE Joint Patient Safety Reporting-JPSR". Resolution: ----------- The post install routine QAN2P34 has been created to update the OUT OF ORDER MESSAGE field (#2), with, "Disabled-USE Joint Patient Safety Reporting-JPSR". NOTE: The following list is inclusive and some sites may not have all listed options. There is no cause for concern if your site does not have some of these listed options. Option Name Type New/Modified/Deleted ----------------- ---- -------------------- QAN AUTO E-MAIL BRIEF R Modified QAN AUTO E-MAIL DELETE R Modified QAN AUTO E-MAIL FULL R Modified QAN BRIEF EDIT R Modified QAN DBASE INTEGRITY CHECKER R Modified QAN EARLY WARNING SYSTEM AUTO R Modified QAN EARLY WARNING SYSTEM MAN R Modified QAN INCIDENT FOLLOW-UP R Modified QAN INCIDENT LOCATION R Modified QAN INCIDENT MAIL TO REGION R Modified QAN INCIDENT QUICK R Modified QAN INCIDENT REGION STATUS R Modified QAN INCIDENT REPORT R Modified QAN INCIDENT STATUS ENTER/EDIT R Modified QAN INCIDENT SUMMARY REGION R Modified QAN INCIDENT WORKSHEET R Modified QAN PATIENT MANIPULATION R Modified QAN PATIENT/INCIDENT VIEW R Modified QAN RECORD MANIPULATION R Modified QAN SITE PARAMETERS ENTER/EDIT R Modified QAN FR ENTER/EDIT R Modified QAN FR PRINT R Modified QAN BOI ENTER/EDIT R Modified QANSERV R Modified QAN FR DELETE R Modified QAN MANUAL FORM UPDATE R Modified QAN MANUAL FORM NOTIFICATION R Modified QAN IR MANUAL UPDATE R Modified QAN IR MANUAL NOTIFICATION R Modified QANERC R Modified QAN TEST R Modified QAN TRANSMIT R Modified QAN PRINT IR R Modified Test Sites: ----------- North Texas HCS (Dallas) Maine HCS (Togus) Software and Documentation Retrieval Instructions: -------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext Filename Description ======= ======================================================== irtm.pdf Incident Reporting V 2.0 Technical Manual irum.pdf Incident Reporting V 2.0 User Manual NOTE: These files must be transferred using the binary (BIN) file transfer mode. The complete and updated User Manual will be posted to the VDL immediately after the release of the patch. Installation Instruction: Pre/Post Installation Overview: ------------------------------- This patch may be installed with users on the system although it is recommended it be queued to run after normal business hours to minimize potential disruption to users. This patch should take less than 5 minutes to install. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Incident+Reporting/Patches/QAN_2.0_34

Patch Subject: CLOZAPINE SETTINGS ISSUE WITH DRUG ENTER/EDIT Description: ============ This patch will resolve the following issue: The drug file entry will not let you add the labs associated with the drug Clozapine that needs labs attached so that drug checks can be performed. Associated Defect Ticket(s): ============================ 1) INC2574335 - Our drug file entry will not let me add the labs associated with the drug Clozapine that needs labs attached so that drug checks can be performed. Associated NSR(s): ================== N/A Patient Safety Issues: ====================== Health I.T. Patient Safety#: HITPS-6411. TICKET OVERVIEW: ================ 1) INC2574335 Problem: -------- North Texas VAMC reported a problem when trying to use the Drug Enter/Edit [PSS DRUG ENTER/EDIT] option to mark a dispense drug as a 'Clozapine' drug. After entering the lab test (WBC) and Specimen Type (BLOOD) they would get a double question mark (??) after answering 'YES' at the 'Is this Correct?' prompt. Resolution: ----------- The problem was a result of an internal call to VA FileMan to save the lab test data. VA FileMan was getting lost because it found more than one match to the Internal Entry Number (IEN) for 'BLOOD' in the TOPOGRAPHY FIELD (#61) file because it did not restrict the lookup to IEN only and other entries in that file had the ABBREVIATION (#6) field set with a value that matched the IEN for 'BLOOD'. Technical Resolution: --------------------- Changed the routine PSSCLOZ at CLOZAD2+2 to use 4 slashes (////) instead of 3 slashes (///) when saving SPECIMEN TYPE (#2) field, as shown below: S DIC("DR")="2////"_PSSPTYN_";3///"_PSSTUFF Test Sites: ----------- Atlanta VA Health Care System VA North Texas Health Care System Pre/Post Installation Overview: ------------------------------- It is not necessary to disable any options. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Pharmacy+Data+Management/Patches/PSS_1.0_232

Patch Subject: DRUG CLASS NOT KILLED Description: ============ This patch will resolve the following issue. INC1144685 - Tramadol listed in two classes Defect Tracking System Ticket(s) & Overview: -------------------------------------------- INC1144685 - Tramadol listed in two classes Problem: -------- It was reported that if the drug class is changed, the "VAC" cross-reference between drug class (NATIONAL DRUG CLASS field #25) and the DRUG file (#50) items are not cleaned up, both the old entry and the new entries still exist. Resolution: ----------- This patch carries changes to logic of updating the VA CLASSIFICATION field (#2) of the DRUG file (#50) to delete the old class when updating the drug class. Also, the 'VAC' index will be re-indexed as part of the post-install routine. Patient Safety Issues (PSIs): ----------------------------- N/A Test Sites: ----------- DANVILLE, ILL ROSEBURG, OR -VAMC Pre/Post Installation Overview: ------------------------------- - The Post-install routine, PSS235PO, will re-index the 'VAC' cross-reference of NATIONAL DRUG CLASS field (#25) of the DRUG file (#50). - The PSS235PO routine will be deleted at the end of patch installation. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Pharmacy+Data+Management/Patches/PSS_1.0_235

Patch Subject: MASTER VETERAN INDEX VISTA ENHANCEMENTS - SUPPORT LONG NAMES IN VA MPI Description: ============ NOTE: To prevent legacy systems ending up as Treating Facilities, RG* and MPIF* patches should NOT be installed on legacy systems or the FORUM CLAIMS system (since it is NOT a Veterans Affair Medical Center (VAMC) VistA system). RG*1.0*67, RG*1.0*68 and MPIF*1.0*69 are the required builds for patch RG*1.0*71. NOTE: Master Patient Index (MPI) 'Support for Long Names in VA MPI' enhancements are being distributed in three VistA namespaces: DG, MPIF and RG. The only build enforced requirement for this set of related patches is that MPIF*1.0*69 be installed before RG*1.0*71. (Do NOT install MPIF*1.0*69 or RG*1.0*71 on legacy sites or on the FORUM CLAIMS system) NOTE: Legacy sites and the FORUM CLAIMS system can install just the DG*5.3*974 patch. MPIF*1.0*69 and RG*1.0*71 should NOT be installed on legacy sites or on the FORUM CLAIMS system. The following enhancements exported in this patch were needed to support the collection of the patient's legal name in the Veteran Affairs (VA) Master Person Index, which requires MPI to support storing patient names and aliases greater than the VistA maximum of 30 characters in length and to also allow updating of Date of Death metadata when the update is triggered through the Override process in Toolkit. Enhancement #1 MPI as of patch MPI*1.0*125 will start supporting the collection of an individual's legal name, which can now exceed VistA's limitation of a maximum length of 30 characters on the name and/or alias fields. To support this change on the MPI, VistA has been modified with the following change so that it will NOT outright reject the value for exceeding the 30-character maximum length: The processor for the incoming Admit Discharge Transfer (ADT) A08 (Update Patient) Health Level Seven (HL7) messages has been modified so that when a Patient's name and/or alias exceeds 30 characters and the NEW Name Components flag is NOT set that a shortened name will be generated from the component parts of the name that were sent in the HL7 message. That shortened version of the name is then filed into the NAME field (#.01) or ALIAS (#1) multiple NAME (#.01) field in the PATIENT (#2) file. NOTE: Prior to this change, long names (Patient Name or Aliases) would have been rejected by the input transform and the update would have failed. If the NEW Name Components flag is set to '1' then the name components for the 'Name' and 'Aliases' values will be filed directly into the NAME COMPONENTS (#20) file. The existing 'ANAME' MUMPS cross-reference (X-REF) on the name components fields in the NAME COMPONENTS (#20) file will continue to be used to update the corresponding NAME (#.01) and/or ALIAS (#1) multiple NAME (#.01) fields in the PATIENT (#2) file. NOTE: See patch MPIF*1.0*69 for additional information on the NEW Name Components flag stored in the MPI ICN BUILD MANAGEMENT (#984.8) file. Enhancement #2 The Healthcare Identity Management (HC IdM) business group has requested an enhancement that will modify routine RGADTP3 to NOW allow a patient's Date of Death (DOD) metadata to be updated ONLY if the update was received from the Override (OVR) process in the Person Service Identity Management (PSIM) Toolkit (TK), even if there was no change in the DOD. Currently only SOURCE OF NOTIFICATION (field #.353) in the PATIENT File (#2) will be updated in VistA through this process, as the other DOD metadata items are NOT presently synched out to the sites from the MVI. Note: The OVR process will be identified by the ARRAY("TKOVRDOD") flag. Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted --------------------------- -------------------- N/A Additional Information: New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A Defect Tracking System Ticket(s) & Overview ------------------------------------------- N/A Test Sites: ---------- Birmingham VAMC Salt Lake City HCS Patch Installation: Pre/Post Installation Overview ------------------------------ There are no Pre/Post installation routine processes. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Clinical+Information+Resource+Network/Patches/RG_1.0_71

Patch Subject: AUTO UPLOAD PERMANENT MAILING ADDRESS Description: ============ Patch IVM*2.0*177 is being released to support the enhancements for the Enterprise Health Benefits Determination (EHBD) program that focuses on updates for the Enrollment System Modernization (ESM) Phase 2 project. As part of the HL7 messaging from the Enrollment System (ES) to Veterans Health Information System and Technology Architecture (VistA) Registration, Eligibility & Enrollment (REE), patient demographic information is sent to VistA sites where the patient is known. Since October 2018, over fifty-one thousand (51,000) Veterans had their addresses updated in ES more than four times. Based on spot checks, most of those updates were due to VistA rejecting the most recent address updates and sending the old address back to ES as a new address update. Background Information: ----------------------- When the Enrollment System (ES) receives a demographic update for a patient, an ORU-Z05, Demographic Data Transmission, is sent to all treating facilities where the patient is known. Currently, for patients with an active prescription, the Permanent Mailing Address is uploaded to a temporary location for display and manual verification in the DEMOGRAPHICS UPLOAD [IVM UPLOAD DEM] option. The demographic data is retained for 14 days. If not reviewed and accepted by a user within that timeframe, the address update is rejected, if the patient still has an active prescription on file at the VistA site. The IVM BACKGROUND JOB [IVM BACKGROUND JOB] handles the review process. If the address is rejected by a user or if it is not reviewed within 14 days and the patient still has an active prescription, the Permanent Mailing Address on file at the VistA site is sent back to ES with a date/time stamp of the current day. ES processes the Z07 message as a new address update for the patient. As a result, old address updates (instead of the most current addresses) are propagated across the VA enterprise. New Functionality: ------------------ With installation of patch IVM*2.0*177, the processing of the HL7 ORU-Z05 message from ES is modified to eliminate the check for an active prescription. If an incoming Permanent Mailing Address change is determined to be the most current, the update(s) will be directly uploaded to the PATIENT file (#2). The BAD ADDRESS INDICATOR (#.121) field is no longer considered in determining whether to upload the address. The DEMOGRAPHICS UPLOAD [IVM UPLOAD DEM] option should not be used to accept or reject Permanent Mailing Address Updates. For those records still pending in the IVM UPLOAD DEMOGRAPHIC TOOL at the time the patch is installed, if an address change is rejected via the IVM BACKGROUND JOB, no HL7 message acknowledgement or HL7 ORU-Z07 address update is sent to ES. The existing functionality is retained which removes the pending address update record from the IVM PATIENT file (#301.5) 14 days after the update was received. Therefore, 14 days after patch IVM*2.0*177 is installed, the IVM UPLOAD DEMOGRAPHIC TOOL will no longer display any Permanent Mailing Addresses. Listing of Updates: =================== Patch IVM*2.0*177 makes the following changes to VistA REE: 1. The processing of the HL7 ORU-Z05 message from ES is modified to eliminate the check for an active prescription and BAD ADDRESS INDICATOR (#.121) so that Permanent Mailing Address fields are automatically uploaded to the PATIENT file (#2) if the change date/time is more recent than what is in the PATIENT file (#2). The Permanent Mailing Address fields that are loaded are as follows: a. ADDRESS CHANGE DT/TM (#.118) b. ADDRESS CHANGE SITE (#.12) c. ADDRESS CHANGE SOURCE (#.119) d. CITY (#.114) e. COUNTY (#.117) f. COUNTRY (#.1173) g. POSTAL CODE (#.1172) (zip code) h. PROVINCE (#.1171) i. STATE (#.115) j. STREET ADDRESS [LINE 1] (#.111) k. STREET ADDRESS [LINE 2] (#.112) l. STREET ADDRESS [LINE 3] (#.113) m. STREET ADDRESS CASS INDICATOR (#.1118) n. BAD ADDRESS INDICATOR (#.121) 2. The IVM Background Job [IVM BACKGROUND JOB] is modified to no longer trigger an ORU-Z07 message to ES after a pending address update is rejected due to the 14-day expiration. Per existing functionality, the pending address update is removed from the IVM PATIENT file (#301.5) after the 14-day expiration. Therefore, 14 days after patch IVM*2.0*177 is installed, the IVM UPLOAD DEMOGRAPHIC TOOL will no longer display any Permanent Mailing Addresses. Patch Components: ================= Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: N/A New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- N/A Test Sites: ----------- VISN 15 VA Kansas City Health Care System VA Pittsburgh Healthcare System Software and Documentation Retrieval Instructions: ---------------------------------------------------- This software is being released as a patch (PackMan) message. Updated documentation describing the new functionality introduced by this patch is available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www.domain.ext/vdl/ Title File Name SFTP Mode -------------------------------------------------------------------------- Release Notes IVM_2_P177_RN.PDF (binary) IVM User Manual IVM_2_P177_UM.PDF (binary) Patch Installation: Pre/Post Installation Overview: ------------------------------- Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Income+Verification+Match/Patches/IVM_2.0_177

Patch Subject: MCCF EDI TAS EPAYMENTS BUILD 7/8 Description: ============ Below is a list of all the applications involved in this patch along with their patch number: APPLICATION/VERSION PATCH --------------------------------------------------------------- ACCOUNTS RECEIVABLE (PRCA) V. 4.5 PRCA*4.5*332 INTEGRATED BILLING (IB) V. 2.0 IB*2.0*633 The patches (PRCA*4.5*332 and IB*2.0*633) are being released in the Kernel Installation and Distribution System (KIDS) multi-build distribution as PRCA_IB_EPAYMENTS_BUNDLE_4_0.KID. The purpose of this patch is to meet the requirements of the Medical Care Collection Fund (MCCF) Electronic Data Interchange (EDI) Transaction Application Suite (TAS) Phase 1 project as related to Accounts Receivable (PRCA). This project ensures the Department of Veterans Affairs (VA) compliance with Electronic Funds Transfer (EFT) and Electronic Remittance Advice (ERA) Operating Rules, and enables VA to more effectively use ERA data, resulting in better revenue and cash flow management. It will provide the infrastructure foundation for electronic exchange of claim payment information and promotes an interoperable system. It will reduce the time elapsed between receipt of the EDI 835 Electronic Remittance Advice Transaction and receipt of the Cash Concentration or Disbursement (CCD+) transactions. It will ensure that trace numbers between payments and remittances can be used by VA, reducing the level of open accounts receivable, allow claim denials to be more quickly addressed, and standardizes Electronic Funds Transfer (EFT) & ERA enrollment to reduce workload burden on VA staff. This patch contains changes to the ePayments (835 and EFT) program area to ensure compliance. Specifically, enhancements to the Veterans Health Information Systems and Technology Architecture (VistA) Third Party EDI Lockbox module to increase timely and accurate processing of payments for electronic claims in compliance with Health Insurance Portability and Accountability Act (HIPAA) and Veterans Health Administration (VHA) Fiscal Accounting policies. The ePayments system is used by Accounts Receivable (AR) staff to process payments from third party payers for both medical and pharmacy claims. The following features of the PRCA software will be affected by this patch. 1. A new report EEOBs marked for Auto-Post Report (EMA) [RCDPE MARKED AUTO-POST REPORT] was added to the EDI LOCKBOX REPORTS Menu [RCDPE EDI LOCKBOX REPORTS MENU]. a) Allows the user to identify the users that marked an EEOB for auto-posting for a specified date range and other filter criteria. 2. A new report Pending EFT Override Report (PEO) [RCDPE EFT OVERRIDE REPORT] was added to the EDI LOCKBOX REPORTS Menu [RCDPE EDI LOCKBOX REPORTS MENU]. a) Shows a listing of unposted medical EFTs that are older than the limit set in the NUMBER OF DAYS (AGE) OF UNPOSTED MEDICAL EFTS TO PREVENT POSTING parameter in a list manger. 3. A new option Duplicate ERA Worklist (DUP) [RCDPE DUPLICATE ERA WORKLIST] was added to the EDI LOCKBOX Menu [RCDPE EDI LOCKBOX MENU]. a) Allows the user to see all the incoming ERA messages that were determined to be duplicates. b) For each duplicate in the list, the user can view the detail, delete the duplicate or file the duplicate as a new ERA. If the user files the duplicate as new ERA, 'DUP' is appended to the end of the trace number to indicate that the ERA was created from a duplicate. 4. A new report Auto Parameter History Report [RCDPE AUTO PARAM HIST REPORT] was added to the Site Parameter Edit menu of the Supervisor's AR Menu. a) Displays a history of changes to auto-activity site parameters. 5. The user initials column on the List or Receipts Report [RCDP LIST OF RECEIPTS REPORT] was expanded to show the first four letters of the user's last name followed by a comma followed by the first letter of the user's first name. Note: if the receipt was processed by the Nightly job, the user's initials will remain 'ar'. 6) A change was made to the EFT/ERA Trending Report (ETR) [RCDPE EFT-ERA TRENDING REPORT] to show the 'TOTAL DIFFERENCE BETWEEN ERAs (PAID) - EFTs (COLLECTED): ' as the last line of the first page instead of the first line of the second page when the report is run in 'GRAND TOTALS ONLY' mode. 7. The following changes were made to the Active Bills With EEOB Report (AB) [RCDPE ACTIVE WITH EEOB REPORT] a) The filter question 'RUN REPORT FOR (A)LL EEOBs or (Z)ERO PAYMENT EEOBs only: ALL//' was changed to 'RUN REPORT FOR (P)AYMENT EEOBs or (Z)ERO PAYMENT EEOBs or (A)LL: ALL//' b) The report now includes EEOBs with a posting status of 'NOT POSTED' or removed. Previously, these were omitted from the report 8. The following changes were made to the 'Manual Match' [RCDPE EFT ERA MANUAL MATCH] action on the ERA WORKLIST [RCDPE EDI LOCKBOX WORKLIST]. a) The name of the action was changed to 'ERA Manual Match'. b) After entering filtering criteria, a new list manager form is displayed to show all the EFTs that partially match the ERA in weighted order such that the most likely EFT matches are displayed at the top and the least likely matches are displayed at the bottom. EFTs that only match the ERA by the payer TIN are not displayed in the list. 9. A new parameter 'NUMBER OF DAYS (AGE) OF UNPOSTED MEDICAL TRICARE TO PREVENT POSTING:' was added to the EDI Lockbox Parameters [RCDPE EDI LOCKBOX PARAMETERS]. a) The default of the new parameter is 30. The range is 14-60 b) Any time the value of this parameter is changed, the change is reflected in the EDI Lockbox Parameters Audit Report [RCDPE PARAMETER AUDIT REPORT]. c) If the user tries to select an ERA associated with a Tricare Payer in the ERA WORKLIST [RCDPE EDI LOCKBOX WORKLIST], that contains EFTs older than the new site parameter, a lock-out error message is displayed. d) The user may override the Tricare lock-out using the Unposted EFT Override [RCDPE UNPOSTED EFT OVERRIDE] menu option. 10. The 'Mismatched Procedure Code' error message that is displayed in the Third Party Joint Inquiry [IBJ THIRD PARTY JOINT INQUIRY] on the EP screen when a claim was billed electronically has been changed to 'Claim was not billed electronically'. 11. The Extended Check/Trace/Credit Card Search (EX) [RCDP EXTENDED CHECK/CC SEARCH] was modified in the following manner: a) The filter prompt 'Check, Credit Card or Trace #' was changed to 'Check, Credit Card, Trace # or All' with a default of all. b) If 'All' is chosen for the filter above, the target string will be searched as a Check, Credit Card and Trace #. If all is not chosen, the target string is only checked for selected search type. c) a minimum of three characters is required to perform the search. d) The search is case insensitive such that a search for trace number containing 'zzz' will also show results where the trace # contains 'ZZZ'. e) If the user does NOT select 'All' as a search filter and the target string is not found, the user is then asked to perform a new search for the same target but a different search type. 12. When the user splits/edits a claim on an ERA line and puts all the payment dollars into suspense, the associated EEOB is no longer removed from the ERA Line. An EEOB is only removed from an ERA line when all of the payment dollars have been distributed to other claims. 13. The Receipt Processing [RCDP RECEIPT PROCESSING] option has been modified in the following manner: a) When the user selects the Customize [RCDP DEPOSIT PROFILE CUSTOMIZ] action, prompt 'Do you want to show check, and credit card information?' has been modified to 'Do you want to show trace #, check, and credit card information?'. b) If the type of payment of the receipt is 'EDI LOCKBOX', then the trace # displays in lieu of the check and/or credit card information. 14. The Nightly AR Process has been modified in the following manner: a) A new site parameter 'ENABLE AUTO-AUDIT FOR TRICARE ELECTRONIC BILLS (Y/N): No//' has been added to the EDI Lockbox Parameters [RCDPE EDI LOCKBOX PARAMETERS] after the auto-audit parameter for Pharmacy. b) Any time the value of this parameter is changed, the change is reflected in the EDI Lockbox Parameters Audit Report [RCDPE PARAMETER AUDIT REPORT]. c) If auto-auditing of Tricare claims is turned on all new bills for claims with payers flagged as Tricare will be audited. 15. The EDI Lockbox (ePayments) Reports Menu [RCDPE EDI LOCKBOX REPORTS MENU] has been re-organized with the following new sub-menus: a) A new sub-menu 'Workload Reports' [RCDPE EDI LOCKBOX REPORTS WORKLOAD MENU] was added to allow access to all of the workload reports as follows: 1. EFT Daily Activity Report [RCDPE EDI LOCKBOX ACT REPORT] 2. EFT Unmatched Aging Report [RCDPE EFT AGING REPORT] 3. ERA Unmatched Aging Report [RCDPE ERA AGING REPORT] 4. Pending EFT Override Report [RCDPE EFT OVERRIDE REPORT] 5. Unapplied EFT Deposits Report [UNAPPLIED EFT DEP REPORT] b) A new sub-menu 'Adjustment Code Reports' [RCDPE EDI LOCKBOX REPORTS ADJ CODE MENU] was added to allow access to all of the workload reports as follows: 1. 835 CARC Data Report [RCDPE CARC CODE PAYER REPORT] 2. Provider Level Adjustments Report [RCDPE PROVIDER LVL ADJ REPORT] 3. CARC/RARC Quick Search [RCDPE CARC/RARC QUICK SEARCH] 4. CARC/RARC Table Data Report [RCDPE CARC/RARC TABLE REPORT] c) A new sub menu 'Additional Research Reports' [RCDPE EDI LOCKBOX REPORTS RESEARCH MENU] was added to allow access to all of the research reports as follows: 1. EFT/ERA TRENDING Report [RCDPE EFT-ERA TRENDING REPORT ] 2. Active Bills With EEOB Report [RCDPE ACTIVE WITH EEOB REPOR] d) A new sub menu 'Audit Reports' [RCDPE EDI LOCKBOX REPORTS AUDIT MENU] was added to allow access to all of the audit reports as follows: 1. Auto-Decrease Adjustment report [RCDPE AUTO-DECREASE REPORT] 2. Auto-Post Report [RCDPE AUTO-POST REPORT] 3. Auto-Posted Receipt Report [RCDPE AUTO-POST RECEIPT REPORT] 4. Auto Parameter History Report [RCDPE AUTO PARAM HIST REPORT] 5. EFT Transaction Audit Report [RCDPE EFT TRANSACTION AUD REP] 6. ERA Status Change Audit Report [RCDPE ERA STATUS CHNG AUD REP] 7. Duplicate EFT Deposits Audit Report [RCDPE EFT AUDIT REPORT] 8. EEOB Move/Copy/Remove Audit Report [RCDPE EEOB MOVE/COPY/RMOVE RPT]. 9. EEOBs Marked for Auto-Post Audit Report [RCDPE MARKED AUTO-POST REPORT]. 10. ERAs Posted with Paper EOB Audit Report [RCDPE ERA W/PAPER EOB REPORT]. 11. Payer Implementation Report [RCDPE PAYER EXCLUSION NAME TIN] 12. [Remove ERA from Active Worklist Audit Report RCDPE REMOVED ERA AUDIT]. 16. The RCDPEAR security key was removed from the Administrative Cost Adjustment [PRCAF ADJ ADMIN] menu option. 17. The Viewing/Printing of ERA information has been modified to allow the user to view it in a list manager so that specific information can be searched for easily. The following areas were changed: a) The View/Print ERA [RCDPE VIEW/PRINT ERA] menu option. b) The View/Print ERA action [RCDPE ERA LIST VIEW ERA] on the ERA Worklist [RCDPE EDI LOCKBOX WORKLIST]. c) The View/Print ERA action [RCDPE APAR VIEW/PRINT ERA] from the Auto-Post Awaiting Resolution (APAR) Worklist [RCDPE APAR]. 18. The Refresh Line action was added to Auto-Post Awaiting Resolution (APAR) RCDPE APAR. The refresh line action allows the user to refresh Split/Edit a Line actions that haven't been auto-posted yet. Patch Components ================ Files & Fields Associated: File Name (#) New/Modified/ Sub-file Name (#) Field Name (Number) Deleted ------------------- ----------------------------- ------------- AR SITE PARAMETER (#342) MODIFIED AUTO-AUDIT TRICARE EDI BILLS (#7.09) NEW AR EDI LOCKBOX MESSAGES (#344.5) MODIFIED DUPLICATE INDICATOR (#.15) NEW RCDPE PARAMETER (#344.61) MODIFIED PHARMACY EFT POST PREVENT DAYS (#.07) MODIFIED TRICARE EFT POST PREVENT DAYS (#.13) NEW TRICARE EFT OVERRIDE (#26) NEW USER - TRICARE OVERRIDE NEW (#27) COMMENT - TRICARE OVERRIDE NEW (#28) HISTORY (#344.611) NEW DATE (#.01) NEW USER (#.02) NEW PARAMETER (#1) NEW DETAIL (#2) NEW OLD VALUE (#3) NEW NEW VALUE (#4) NEW Bulletins Associated: New/Modified/ Bulletin Name Deleted ------------- ------------- N/A Dialogs Associated: New/Modified/ Dialog Name Deleted ----------- ------------- N/A Forms Associated: New/Modified/ Form Name File Name (Number) Deleted --------- ------------------ ------------- N/A Functions Associated: New/Modified/ Function Name Deleted ------------- ------------- N/A HL Logical Link: New/Modified/ HL Logical Name Deleted --------------- ------------- N/A HL7 Application Parameters: New/Modified/ HL7 Parameter Name Deleted ------------------ ------------- N/A HLO Application Registry: New/Modified/ HLO Registry Name Deleted ----------------- ------------- N/A Help Frames Associated: New/Modified/ Help Frame Name Deleted --------------- ------------- N/A Mail Groups Associated: New/Modified/ Mail Group Name Deleted --------------- ------------- N/A Options Associated: Option Name Type SEND/ATTACH ----------- ---- ------------- PRCA BIL AGENCY ACTION ATTACH TO MENU PRCA CBO PARAMETERS RUN ROUTINE ATTACH TO MENU PRCA DEACTIVATE GROUP ACTION ATTACH TO MENU PRCA NOTIFICATION PARAMETERS ACTION ATTACH TO MENU PRCA RC PARAMETERS RUN ROUTINE ATTACH TO MENU PRCA SITE PARAMETER MENU SEND TO SITE PRCAF U ADMIN.RATE ACTION ATTACH TO MENU RCDP EXTENDED CHECK/CC SEARCH RUN ROUTINE SEND TO SITE RCDPE ACTIVE WITH EEOB REPORT RUN ROUTINE ATTACH TO MENU RCDPE APAR RUN ROUTINE ATTACH TO MENU RCDPE AUTO PARAM HIST REPORT RUN ROUTINE SEND TO SITE RCDPE AUTO-DECREASE REPORT RUN ROUTINE ATTACH TO MENU RCDPE AUTO-POST RECEIPT REPORT RUN ROUTINE ATTACH TO MENU RCDPE AUTO-POST REPORT RUN ROUTINE ATTACH TO MENU RCDPE CARC CODE PAYER REPORT RUN ROUTINE ATTACH TO MENU RCDPE CARC/RARC QUICK SEARCH RUN ROUTINE ATTACH TO MENU RCDPE CARC/RARC TABLE REPORT RUN ROUTINE ATTACH TO MENU RCDPE DUPLICATE ERA WORKLIST ACTION SEND TO SITE RCDPE EDI LOCKBOX ACT REPORT RUN ROUTINE ATTACH TO MENU RCDPE EDI LOCKBOX ADJCDE RPRTS MENU SEND TO SITE RCDPE EDI LOCKBOX ARSRCH RPRTS MENU SEND TO SITE RCDPE EDI LOCKBOX AUDIT RPRTS MENU SEND TO SITE RCDPE EDI LOCKBOX MENU MENU SEND TO SITE RCDPE EDI LOCKBOX PARAMETERS RUN ROUTINE ATTACH TO MENU RCDPE EDI LOCKBOX REPORTS MENU MENU SEND TO SITE RCDPE EDI LOCKBOX WORKLD RPRTS MENU SEND TO SITE RCDPE EDI LOCKBOX WORKLIST RUN ROUTINE ATTACH TO MENU RCDPE EEOB MOVE/COPY/REMOVE RUN ROUTINE ATTACH TO MENU RCDPE EEOB MOVE/COPY/RMOVE RPT RUN ROUTINE ATTACH TO MENU RCDPE EFT AGING REPORT RUN ROUTINE ATTACH TO MENU RCDPE EFT AUDIT REPORT RUN ROUTINE ATTACH TO MENU RCDPE EFT OVERRIDE REPORT RUN ROUTINE SEND TO SITE RCDPE EFT TRANSACTION AUD REP RUN ROUTINE ATTACH TO MENU RCDPE EFT-ERA TRENDING REPORT RUN ROUTINE ATTACH TO MENU RCDPE ERA AGING REPORT RUN ROUTINE ATTACH TO MENU RCDPE ERA POSTED BY PAPER EOB RUN ROUTINE ATTACH TO MENU RCDPE ERA STATUS CHNG AUD REP RUN ROUTINE ATTACH TO MENU RCDPE ERA W/PAPER EOB REPORT RUN ROUTINE ATTACH TO MENU RCDPE EXCEPTION PROCESSING RUN ROUTINE ATTACH TO MENU RCDPE EXCLUSION AUDIT REPORT RUN ROUTINE ATTACH TO MENU RCDPE MANUAL MATCH EFT-ERA RUN ROUTINE SEND TO SITE RCDPE MARK 0-BAL EFT MATCHED RUN ROUTINE ATTACH TO MENU RCDPE MARKED AUTO-POST REPORT RUN ROUTINE SEND TO SITE RCDPE MATCH EFT TO ERA RUN ROUTINE ATTACH TO MENU RCDPE PARAMETER AUDIT REPORT RUN ROUTINE ATTACH TO MENU RCDPE PAYER EXCLUSION NAME TIN RUN ROUTINE ATTACH TO MENU RCDPE PAYER IDENTIFY RUN ROUTINE ATTACH TO MENU RCDPE PROVIDER LVL ADJ REPORT RUN ROUTINE ATTACH TO MENU RCDPE REMOVE DUP DEPOSITS RUN ROUTINE ATTACH TO MENU RCDPE REMOVE ERA FROM WORKLIST RUN ROUTINE ATTACH TO MENU RCDPE REMOVED ERA AUDIT RUN ROUTINE ATTACH TO MENU RCDPE SITE PARAMETER REPORT RUN ROUTINE ATTACH TO MENU RCDPE UNAPPLIED EFT DEP REPORT RUN ROUTINE ATTACH TO MENU RCDPE UNMATCH ERA RUN ROUTINE ATTACH TO MENU RCDPE UNPOSTED EFT OVERRIDE RUN ROUTINE ATTACH TO MENU RCDPE VIEW/PRINT ERA RUN ROUTINE ATTACH TO MENU Parameter Definitions: New/Modified/ Parameter Name Deleted -------------- ------------- N/A Parameter Template: New/Modified/ Template Name Deleted ------------- ------------- N/A Protocols Associated: Protocol Name SEND/ATTACH ------------- ------------- RCDPE EFT ERA MANUAL MATCH SEND TO SITE RCDPE EFT PARTIAL MATCH MENU SEND TO SITE RCDPE EFT PARTIAL MATCH SELECT SEND TO SITE RCDPEX DELETE DUP MESSAGE SEND TO SITE RCDPEX DUP EXCEPTION MENU SEND TO SITE RCDPEX FILE DUPLICATE MESSAGE SEND TO SITE RCDPEX VIEW/PRINT DUP MESSAGE SEND TO SITE VALM QUIT SEND TO SITE Remote Procedures Associated: New/Modified/ Remote Procedure Name Deleted --------------------- ------------- N/A Security Keys Associated: New/Modified/ Security Key Name Deleted ----------------- ------------- N/A Templates, Input Associated: New/Modified/ Template Name Type File Name (Number) Deleted ------------- ---- ------------------ ------------- N/A Templates, List Associated: Template Name Type SEND/ATTACH ------------- ---- ------------- RCDP LIST OF RECEIPTS REPORT PROTOCOL SEND TO SITE RCDPE EEOB MARKED FOR AP AUDIT PROTOCOL SEND TO SITE RCDPE EFT PARTIAL MATCH PROTOCOL SEND TO SITE RCDPE VIEW ERA DETAIL PROTOCOL SEND TO SITE RCDPEX DUPLICATE ERA LIST PROTOCOL SEND TO SITE Templates, Print Associated: New/Modified/ Template Name Type File Name (Number) Deleted ------------- ---- ------------------ ------------- N/A Templates, Sort Associated: New/Modified/ Template Name Type File Name (Number) Deleted ------------- ---- ------------------ ------------- N/A Additional Information: N/A New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A Defect Tracking System Ticket(s) & Overview --------------------------- N/A Test Sites: ---------- Washington, DC Baltimore MARYLAND HCS Tennessee Valley HCS Dallas NORTH TEXAS HCS Documentation Retrieval Instructions ------------------------------------ Updated documentation describing the new functionality introduced by this patch is available. The preferred method is to retrieve the files from download.vista.domain.ext/. This transmits the files from the first available server. Sites may also elect to retrieve software directly from a specific server. Sites may retrieve the documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ Title File Name SFTP Mode ----------------------------------------------------------------------- Deployment, Installation, prca_4_5_332_ig.pdf Binary Back-Out, and Rollback Guide (PRCA*4.5*332, IB*2.0*633) ePayments User Manual epayments_user_manual_r0619.pdf Binary (EDI Lockbox) AR Technical Manual/ prca_4_5_p332_tm.pdf Binary Security Guide (PRCA*4.5*332) Patch Installation: Pre/Post Installation Overview ------------------------------ Do not install this patch while the "Accounts Receivable Nightly Process Background Job" [PRCA NIGHTLY PROCESS] is running. To avoid disruptions, this patch should be installed during non-peak hours when there is minimal activity on the system and there are no Accounts Receivable users on the system. Use default answers for KIDS load/install questions. Multi-Build: http://code.osehra.org/VistA.git/blob/master/Packages/MultiBuilds/PRCA_IB_EPAYMENTS_BUNDLE_4_0.KIDs

Patch Subject: CURRENT MSE DELETING WITHOUT ADDING INCOMING MSE Description: ============ Patch DG*5.3*975 fixes an issue where the current Military Service Episode (MSE) data is being deleted while processing an incoming ORFZ11 and incoming MSE data is not being stored. Upon receipt of an ORFZ11 Health Level-7 (HL7) message from Enrollment System (ES), Veterans Information Systems and Technology Architecture (VistA) system parses the data within and stores as appropriate. When processing the MSE data contained within the ZMH segment of the ORFZ11, VistA first deletes the MSE data from the PATIENT (#2) file. It then should store the MSE data contained in the ZMH segment of the ORFZ11. Due to a subscripting error introduced by patch DG*5.3*959, the MSE data from the ZMH segment fails to store. In addition, this issue also causes the Service Connected Rated Disabilities to be deleted from VistA and fails to store the Service Connected Rated Disabilities from the ZRD segment of the ORFZ11 into VistA. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A Additional Information: N/A New Service Requests (NSRs): -------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC2693452 - Registration - User reports MSE/SC info not storing in VistA Duplicates: INC1940610 - ES transmissions not uploading INC3001527 - VistA not receiving or storing MSE/MT info from ES at NFL INC4243837 - Enrollment System Problem: --------- Current Military Service Episode data is being deleted from an incoming ORFZ11 and incoming MSE data is not being stored. Upon receipt of an ORFZ11 HL7 message from the ES, VistA parses the data within and stores as appropriate. When processing the MSE data contained within the ZMH segment of the ORFZ11, VistA first deletes the MSE data from the PATIENT (#2) file. It then should store the MSE data contained in the ZMH segment of the ORFZ11. Due to a subscripting error introduced by patch DG*5.3*959, the MSE data from the ZMH segment fails to store. In addition, this issue also causes the Service Connected Rated Disabilities to be deleted from VistA and fails to store the Service Connected Rated Disabilities from the ZRD segment of the ORFZ11 into VistA. Resolution: ----------- Modify routine DGENUPL1 to use the variable IVMRTN in the ^TMP global subscript that holds the incoming data. Test Sites: ----------- West Palm Beach VAMC VA North Florida/South Georgia HCS Software and Documentation Retrieval Instructions: -------------------------------------------------- N/A Documentation Title File Name FTP Mode --------------------------------------------------------------------- N/A Host File Name FTP Mode --------------------------------------------------------------------- N/A Patch Installation: Pre/Post Installation Overview: ------------------------------- Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Registration/Patches/DG_5.3_975

Patch Subject: BUG FIXES TO VA FILEMAN Description: ============ This patch corrects twelve issues with VA FileMan 22.2. These issues were discovered at sites that have installed VA FileMan 22.2 and DI*22.2*10. Patch Components: ----------------- File Name (#) Field Name (#) New/Modified/Deleted ------------- -------------- ------------- AUDIT (#1.1) OLD VALUE (2) Modified NEW VALUE (3) Blood Bank Clearance: --------------------- 2/5/2019 EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch DI*22.2*14 contains changes to a package referenced in ProPath standard titled: BBM Team Review of VistA Patches. This patch does not alter or modify any VistA Blood Bank software design safeguards or safety critical elements functions. RISK ANALYSIS: Changes made by patch DI*22.2*14 have no adverse effect on Blood Bank software functionality, therefore RISK is none. Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. Ticket: I12133765FY17 Problem: Sort templates don't show previous values when editing the template Resolution: Change DIP1 to display previous value 2. Ticket: I10027710FY16 Problem: Date utility, %DT, allows incorrect time. Calling %DT with X=3160707.8 should return Y=-1 Resolution: Change DIDT to return Y=-1 if X contains an incorrect time. Post install routine DI14POST will resave DIDT as %DT. 3. Ticket: R13378947FY17 Problem: Can't print OLD VALUE (#2) and NEW VALUE (#3) fields from AUDIT (#1.1) file Resolution: Change the logic in the computed fields #2 and #3. Replace If statement with $Select. Also, change DINIT20, which sets the logic when FileMan is initialized. 4. Ticket: INC3327007 Problem: Add APPLICATION GROUP to Data Dictionary List File Attributes option Resolution: Change DIDH1 to display APPLICATION GROUP 5. Ticket: INC1570061 Problem: Maximum length of new style cross reference is too short Resolution: Change MAXIMUM LENGTH (#6) field in INDEX (#.11) file from 240 to 999. Add change to DI14POST and DINIT2A4 6. Ticket: INC1550303 Problem: Undefined error when doing an Inquire to a file that has a computed field that calls EN^DIQ1 Resolution: Change DIQ1 to new the variables C and DI at tag EN 7. Ticket: I16938507FY18 Problem: The variable DISYS is undefined when calling EN^DIEZ in background Resolution: Move the call to DT^DICRW to earlier in the routine. It sets DISYS. 8. Ticket: I17087603FY18 Problem: When a partial Data Dictionary containing a multiple is distributed using KIDS, the zero node of sub dictionary has the wrong first piece Resolution: Change DIFROMS2; comment out line that was setting the sub dictionary zero node incorrectly to fix the bug. Post Install EN^DI14POST will check and correct any corrupted sub dictionaries. 9. Ticket: INC0105488 Problem: Queries for data that utilizes a variable pointer field could be missing results Resolution: Change to DICOMP0 to handle variable pointers correctly 10. Ticket: I16902120FY18 Problem: If the variable %DT(0) is defined when an Input Transform is executed, it causes incorrect information Resolution: Change DICN to new the variable before executing the Input Transform 11. Ticket: I17417683FY18, I10449501FY16 Problem: Audit is not recording changes if it happens during a trigger to another file Resolution: The problem is the DA variable is changed. Change DICR to save the DA array and other variables before auditing and then restore the variables 12. Ticket: R15604177FY17 Problem: If the records being transferred is in a file that contain a multiple field that uses DINUM in the Input Transform, then FileMan stacks the DA array, but never unstacks it when it tries to delete the record Resolution: Change DIT0 to reset DA to the correct record before deleting Test Sites: ----------- West Palm Beach, Florida North Chicago, IL Software and Documentation Retrieval Instructions: -------------------------------------------------- Software is being released as a KIDS Build on Forum. Patch Installation: Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/VA+FileMan/Patches/DI_22.2_14

Patch Subject: CRCL AND CREATININE DISPLAY ERROR Description: ============ This patch will resolve the following issue. INC2529214 - Code failure during display of CrCL and Creatinine lab results in the patient profile Defect Tracking System Ticket(s) & Overview: -------------------------------------------- INC2529214 - Code failure or missing data during display of CrCL and Creatinine lab results in the patient profile Problem: -------- Inpatient pharmacists at the Pensacola Joint Ambulatory Care Center reported an error in VistA had occurred during display of the patient profile. When a user accesses the following Inpatient menu options; Inpatient Profile [PSJ PR] Order Entry [PSJU NE] Action Profile #2 [PSJU AP-2] A hard stop will occur or data will not be displayed to the user in VistA due to an undefined variable ZDSPL. This is caused by code that was written in such a way as to not handle all possible combinations of data that could be present. The code specifically would not set ZDSPL if the CrCL value is equal to "Not Found" and the Creatinine value was equal to .01 or if the CrCL was less than 1. The four Inpatient routines involved are PSJHEAD, PSJLMHED, PSJCLOR2 and PSGCAPP0 having the same code so the same fix could be applied to all four routines. Resolution: ----------- The resolution for the undefined variable ZDSPL is to update the code to handle all possible data combinations that could exist for CrCL and Creatinine results. Technical Resolution: --------------------- Changed routines PSJHEAD, PSJLMHED, PSJCLOR2 and PSJCAPP0 to format and display the CrCL and Creatine lab results in the patient profile and correct the undefined variable or un-displayed results. Patient Safety Issues (PSIs): ----------------------------- N/A Test Sites: ----------- Northport VAMC Biloxi VAMC Pre/Post Installation Overview: ------------------------------- It is not necessary to disable any options. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Inpatient+Medications/Patches/PSJ_5.0_387

Patch Subject: CP FLOWSHEETS TERMINOLOGY UPDATES Description: ============ This patch will correct the following issue: The Clinical Procedures (CP) Terminology TERM file (#704.101) contains terms used during data entry/display in CP Flowsheet. The Office of Informatics and Analytics - Applied Informatics Services (AIS) Terminology Review Group submitted a spreadsheet requesting additions or updates of Terms. New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1) INC3510791 - CP Flowsheets Terminology Update Problem: -------- The Clinical Procedures (CP) Terminology TERM file (#704.101) contains terms used during data entry/display in CP Flowsheet. The Office of Informatics and Analytics - Applied Informatics Services (AIS) Terminology Review Group submitted a spreadsheet requesting additions or updates of Terms. The following list documents the approved changes for INC3510791 Newly Added Terms: ------------------ CARDIOVASCULAR: Conditions CARDIOVASCULAR: DVT Prevention CARDIOVASCULAR: JVD Inhaler Musculoskeletal: Ankle ROM Musculoskeletal: Conditions Musculoskeletal: Elbow ROM Musculoskeletal: Wrist ROM NEURO ASSESSMENT: SPEECH NEURO ASSESSMENT: AUDITORY NEURO ASSESSMENT: CORNEAL REFLEX NEURO ASSESSMENT: COUGH REFLEX NEURO ASSESSMENT: GAG REFLEX NEURO ASSESSMENT: HAND GRIP NEURO ASSESSMENT: MENTAL STATUS NEURO ASSESSMENT: MOTOR LOWER EXTREMITIES NEURO ASSESSMENT: MOTOR UPPER EXTREMITIES NEURO ASSESSMENT: ORIENTATION NEURO ASSESSMENT: PLANTAR (BABINSKI) REFLEX NEURO ASSESSMENT: REFLEXES PRESENT NEURO ASSESSMENT: SEIZURE ACTIVITY NEURO ASSESSMENT: SENSATION LOWER EXTREMITIES NEURO ASSESSMENT: SENSATION UPPER EXTREMITIES NEURO ASSESSMENT: Sensory Testing NEURO ASSESSMENT: Shoulder Shrug NEURO ASSESSMENT: SLEEP NEURO ASSESSMENT: SWALLOW REFLEX NEURO ASSESSMENT: SYMPTOMS NEURO ASSESSMENT: VISION Oral Care: Dentures/Removable Appliance Oral Care: Patient Education Oral Care: Performed/Observed Oral Care: Referral or Consult to Dental/Dental Hygiene Oral Care: Supplies in Room Oral Care: Symptoms or Problems Oral Care: Type PCA: Max Limit Per Hour PERIPHERAL-VASCULAR: Movement Rounding: Patient Off Unit Rounding: Privacy Maintained Rounding: Toileting Modified Terms: --------------- CARDIOVASCULAR: Capillary Refill CARDIOVASCULAR: Cardiac Abnormal Beats Per Minute CARDIOVASCULAR: Cardiac Ectopy CARDIOVASCULAR: Cardiac Rhythm CARDIOVASCULAR: Cardiac Rhythm Lead CARDIOVASCULAR: Edema #1 CARDIOVASCULAR: Edema #2 CARDIOVASCULAR: Edema #3 CARDIOVASCULAR: Edema #4 CARDIOVASCULAR: Edema Amount CARDIOVASCULAR: Edema Severity CARDIOVASCULAR: Heart Sounds CARDIOVASCULAR: PA Catheter Repositioned/Discontinued Reason CARDIOVASCULAR: Pacemaker Atrial mA CARDIOVASCULAR: Pacemaker AV Interval CARDIOVASCULAR: Pacemaker Capture CARDIOVASCULAR: Pacemaker Mode CARDIOVASCULAR: Pacemaker On CARDIOVASCULAR: Pacemaker Rate CARDIOVASCULAR: Pacemaker Sense CARDIOVASCULAR: Pacemaker Sensitivity Atrial CARDIOVASCULAR: Pacemaker Sensitivity Ventricular CARDIOVASCULAR: Pacemaker Type CARDIOVASCULAR: Pacemaker Unit ID CARDIOVASCULAR: Pacemaker Ventricular mA CARDIOVASCULAR: Pacemaker Wires CARDIOVASCULAR: Pulse Strength Enteral Nutrition Type MUSCULOSKELETAL: HIP ROM MUSCULOSKELETAL: JOINT CONDITION MUSCULOSKELETAL: KNEE ROM MUSCULOSKELETAL: SHOULDER ROM NEURO ASSESSMENT: PUPIL NEURO ASSESSMENT: PUPIL SIZE Oral Care Resolution: ----------- The above Additions/Updates will be made to the CP Terminology TERM File (#704.101). The details of each of these terms is in the Clinical Observation (CliO) Terminology Dictionary and Clinical Data Model Documentation that is listed below. Test Sites: ----------- Edward Hines Jr. VA Hospital (IL) Huntington VA Medical Center (WV) Software and Documentation Retrieval Instructions: -------------------------------------------------- Documentation describing the new functionality introduced by this patch is available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Hines: ftp.domain.ext Salt Lake City: ftp.domain.ext File Name: Description: Protocol: ========== ============ ========= MD1_0P68TERM.PDF CliO Terminology Dictionary Binary And Clinical Data Model Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ Patch Installation: =================== Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Clinical+Procedures/Patches/MD_1.0_68

Patch Subject: PPMS PIE SUPPORT Description: ============ XU*8.0*691 and XU*8.0*705 are the required builds for patch XU*8.0*711. The following enhancements exported in this patch are in support of the Provider Profile Management System (PPMS) / Provider Integration Engine (PIE) updates for Mission Act that the Master Veteran Index (MVI) team has been requested to implement. These enhancements listed below work with the MVI changes that have been exported in patch MPI*1.0*130. Enhancement #1 The existing Remote Procedure Call (RPC) [XUS MVI NEW PERSON GET] and its corresponding routine XUMVINPU have been modified to support the additional search requests by National Provider Identifier (NPI) or Social Security Number (SSN) within the NEW PERSON (#200) file. Furthermore, the following data associated with the additional fields listed below will be transmitted from the NEW PERSON (#200) file to MVI for the requested record: - STREET ADDRESS 2 .112 - STREET ADDRESS 3 .113 - CITY .114 - STATE .115 - ZIP CODE .116 - FAX NUMBER .136 - SEX 4 - TITLE 8 - NPI 41.99 - KEYS 51 - PERSON CLASS 8932.1 - PERSON CLASS .01 - EFFECTIVE DATE 2 - EXPIRATION DATE 3 - AUTHORIZED TO WRITE MED ORDERS 53.1 - DETOX/MAINTENANCE ID NUMBER 53.11 - DEA# 53.2 - INACTIVE DATE 53.4 - PROVIDER CLASS 53.5 - PROVIDER TYPE 53.6 - REMARKS 53.9 - NON-VA PRESCRIBER 53.91 - TAX ID 53.92 - SCHEDULE II NARCOTIC 55.1 - SCHEDULE II NON-NARCOTIC 55.2 - SCHEDULE III NARCOTIC 55.3 - SCHEDULE III NON-NARCOTIC 55.4 - SCHEDULE IV 55.5 - SCHEDULE V 55.6 - DEA EXPIRATION DATE 747.44 ** The following NEW fields will ONLY be returned if patch XU*8.0*688 has been installed. ** - NEW DEA #'S 53.21 [200.5321] - DEA NUMBER .01 - INDIVIDUAL DEA SUFFIX .02 - DETOX CALCULATED 9001 ** The following fields from the DEA NUMBERS (#8991.9) file will ONLY be returned if a DEA NUMBER (53.21) entry has been defined. ** - BUSINESS ACTIVITY CODE .02 - DETOX NUMBER .03 - EXPIRATION DATE .04 - USE FOR INPATIENT ORDERS .06 - TYPE .07 - NAME (PROVIDER OR INSTITUTION) 1.1 - STREET ADDRESS 1 1.2 - STREET ADDRESS 2 1.3 - STREET ADDRESS 3 1.4 - CITY 1.5 - STATE 1.6 - ZIP CODE 1.7 - SCHEDULE II NARCOTIC? 2.1 - SCHEDULE II NON-NARCOTIC? 2.2 - SCHEDULE III NARCOTIC? 2.3 - SCHEDULE III NON-NARCOTIC? 2.4 - SCHEDULE IV? 2.5 - SCHEDULE V? 2.6 - LAST UPDATED BY 10.1 - LAST UPDATE DATE/TIME 10.2 - LAST DOJ UPDATE DATE/TIME 10.3 Enhancement #2 The existing RPC [XUS MVI NEW PERSON UPDATE] and corresponding routine XUMVINPU have been modified to allow the following additional fields to be updated by MVI in the NEW PERSON File (#200) for a specific DUZ: - EMAIL ADDRESS (#.151) - NETWORK USERNAME (#501.1) Enhancement #3 A new RPC [XUS MVI ENRICH NEW PERSON] along with the corresponding routines XUMVIENU and XUMVINPA were created to give MVI the ability to 'Add' and/or 'Update' a NEW PERSON (#200) file entry in support of PPMS/PIE in VistA. This RPC 'REQUIRES' the following two parameters: - XUARR - An array containing the new values for the specific fields to 'ADD' or 'UPDATE' the record in the NEW PERSON (#200) file with. Required Elements: ("WHO") : Station Number of requesting station ("NPI") : National Provider Identifier ("NAME") : Surname | First | Middle | Suffix | Full **NOTE: 'NAME' Required only when XUFLAG is 'A'.** Optional Elements (Only pass if update required): ("ADDRESS DATA") : Address values consisting of the following delimited information - Street Address 1 | Street Address 2 | Street Address 3 | City | State | Zip | Office Phone | Fax Number ("SubjectOrgan") : Subject Organization *Defaults to 'Department Of Veterans Affairs' ("SubjectOrganID") : Subject Organization Id *Defaults to 'urn:oid:2.16.840.1.113883.4.349' ("ADUPN") : Identity and Access Management (IAM) Active Directory User Principle Name ("AuthWriteMedOrders") : YES (1) or NO (0) *Defaults to YES (1) if ("WHO") is 200PIEV and ("DEA",<seq#>,"DEA") is transmitted. ("DEA",<seq#>, : Drug Enforcement Agency (DEA) Info (*Multiple Entries Allowed) "DEA") : DEA Number "Detox") : Substance Abuse Provider Detox/Maintenance ID # "DEAExpire") : DEA Number Expiration Date (*Can be a future date.) "SchedIINarc") : YES (1) or NO (0) "SchedIINonNarc") : YES (1) or NO (0) "SchedIIINarc") : YES (1) or NO (0) "SchedIIINonNarc"): YES (1) or NO (0) "SchedIV") : YES (1) or NO (0) "SchedV") : YES (1) or NO (0) ("DEGREE") : Individual's Degree codes separated by a space ("EMAIL") : Email Address ("GENDER") : Male of Female ("Inactivate") : Date Access Inactivated (*Can be a future date.) ("NonVAPrescriber") : YES (1) or NO (0) *Defaults to YES (1) if ("WHO") is 200PIEV. ("NTUSERNAME") : Network User Name ("PersonClass",<seq#>, : Person Class Info (*Multiple Entries Allowed) "PersonClass") : X12 Code Value "PersonClassActive") : Date Class Activated *Defaults to TODAY if NOT currently active. "PersonClassExpire") : Date Class De-Activated ("ProviderClass") : PROVIDER CLASS (#7) file record value ("ProviderType") : Provider Type Code | Provider Type Value ("Remarks") : Provider Remarks *Defaults to 'NON-VA PROVIDER' if ("WHO") is 200PIEV ("SECID") : IAM Security ID ("TaxID") : Tax ID of the Non-VA Physician's Private Clinic ("Termination") : Date Access Terminated (*Can NOT be a future date.) ("Title") : Person's Title *Defaults to 'NON-VA PROVIDER' if ("WHO") is 200PIEV ("UniqueUserID") : IAM's Unique User Id - XUFLAG - "A" : RPC is being called to 'ADD' a record to the NEW PERSON (#200) file. "U" : RPC is being called to 'UPDATE' an existing record in the NEW PERSON (#200) file. Finally, the RPC will return one of the following values to MVI upon execution completion: - DUZ : No issues adding and/or editing an entry. - DUZ^-1^Error Message : Issue occurred editing an entry where some data was invalid and could NOT be filed. - -1^Error Message : Required data NOT passed, entry could NOT be added (Flag="A") or entry could NOT be found to be updated (Flag="U"). Enhancement #4 The business office has requested that the [XUS MVI NEW PERSON DATA] RPC which returns calculated data analysis from the NEW PERSON (#200) file be enhanced to ensure that for a NEW PERSON (#200) record to be determined 'Active' that the record must also have a PRIMARY MENU OPTION (Field #201) assigned. Therefore, the associated routine XUMVIDTA has been modified to include this additional check of ensuring that a NEW PERSON (#200) record has a PRIMARY MENU OPTION (#201) when determining if that user's record is considered 'Active'. Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------------- -------------------- XUS MVI ENRICH NEW PERSON NEW XUS MVI NEW PERSON GET MODIFIED XUS MVI NEW PERSON UPDATE MODIFIED Parameter Definitions Associated: Parameter Name New/Modified/Deleted --------------------------- -------------------- N/A Additional Information: Blood Bank Team Coordination ---------------------------- EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch XU*8.0*711 contains changes to a package referenced in ProPath standard titled: BBM Team Review of VistA Patches. This patch does not alter or modify any VistA Blood Bank software design safeguards or safety critical elements functions. RISK ANALYSIS: Changes made by patch XU*8.0*711 have no adverse effect on Blood Bank software functionality, therefore RISK is none. New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A Defect Tracking System Ticket(s) & Overview ------------------------------------------- N/A Patch Installation: Pre/Post Installation Overview ------------------------------ There are no pre/post installation routines in this patch. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Kernel/Patches/XU_8.0_711

Patch Subject: ADD VET360 TO ADDRESS CHANGE SOURCE Description: ============ Patch IVM*2*182 will fix the following issue: -Code VET360 not found in IVM ADDRESS CHANGE LOG (#301.7) file in ADDRESS CHANGE SOURCE (#3) field. Patch Components: ----------------- N/A Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- IVM ADDRESS CHANGE LOG (#301.7) ADDRESS CHANGE SOURCE (#3) Modified Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Parameter Definition Associated: Parameter Definition Name New/Modified/Deleted ------------------------ -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Remote Procedure Call: RPC NAME New/Modified/Deleted -------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: N/A New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- INC5216655 - Code VET360 not found in file 301.7 address change source field. Problem: -------- The business owners have requested 'VET360' be added as a selection to the ADDRESS CHANGE SOURCE (#3) Field in the IVM ADDRESS CHANGE LOG (#301.7) File. This field should match the values available in ADDRESS CHANGE SOURCE (#.119) Field in the PATIENT (#2) File. Otherwise there may be issues utilizing FileMan utilities in the future. Resolution: ----------- We have updated the data dictionary for the ADDRESS CHANGE SOURCE (#3) Field in the IVM ADDRESS CHANGE LOG (#301.7) File to contain the option 'VET360'. This will resolve any potential issues. TEST SITES: ----------- Cincinnati VAMC Clarksburg VAMC Beckley VAMC Altoona VAMC Software and Documentation Retrieval Instructions: -------------------------------------------------- N/A Patch Installation: Pre/Post Installation Overview: ------------------------------- This patch may be installed with users on the system although it is recommended it be queued to run after normal business hours to minimize potential disruption to users. This patch should take less than 5 minutes to install. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Income+Verification+Match/Patches/IVM_2.0_182

Patch Subject: MANAGEMENT EDIT CHANGES Description: ============ Patch DG*5.3*978 is being released to support the enhancements for the Enterprise Health Benefits Determination (EHBD) program that focuses on updates for the Enrollment System Modernization (ESM) Phase 2 project. NOTE: DG*5.3*978 is being released with IVM*2.0*180 in Host File DG_53_P978.KID. Patch DG*5.3*978 is also being released in support of the Enrollment System (ES) 5.6 release. Refer to Informational Patch EAS*1*178 (Enrollment Application System) for additional details regarding the ES release. Veterans Health Information System and Technology Architecture (VistA) Registration, Eligibility & Enrollment (REE) currently does not allow a user to request an initial appointment for a newly enrolled Veteran after registration. Welcome To My VA (W2myVA) makes an outbound call from a VA representative in conjunction with the introductory letter and personalized handbook each Veteran receives upon enrollment. If the Veteran requests an appointment during that conversation, the VistA Preferred Facility cannot change the Appointment Request to YES. As a result, the Veteran will not show on the local New Enrollee Appointment Request (NEAR) list to disposition the Veteran's appointment. The Veteran is kept on the W2myVA reports, negatively impacting the W2myVA reporting that captures the total amount of time Veterans wait to be scheduled for an appointment. Patch DG*5.3*978 provides a mechanism for updating the appointment request field from NO to YES after registration via the Management Edit [DGEN NEACL REQUEST MGT EDIT] option. The Management Edit Call List [DGEN NEACL MGT RPT1] and Tracking Report [DGEN NEACL MGT RPT2] options are modified, and new fields are added to the database to track the original appointment request and original request date made during registration. Currently there is no mechanism for a VistA user to add a Veteran to the local NEAR list, unless the user indicates the Veteran wants to be seen by a doctor when completing a VA Form 10-10EZ in ES, VistA, or online. When the New Enrollee makes an appointment request at the W2myVA follow-up phone call, VistA users at the Preferred Facility or an associated Satellite Facility need the ability to change the response from NO to YES. Once the appointment is requested, it places the Veteran on the local NEAR list (Call List [DGEN NEACL MGT RPT1], Call List (background job) [DGEN NEACL MGT RPT1BK] and the Tracking Report [DGEN NEACL MGT RPT2] options). This allows a VistA user to disposition the appointment request in the Management Edit [DGEN NEACL REQUEST MGT EDIT] option. Lack of this functionality impacts accurate reporting of the total amount of time Veterans wait to be scheduled for an appointment. The Management Edit [DGEN NEACL REQUEST MGT EDIT] option is updated to either present an appointment request prompt to the user or to present the current prompts for dispositioning an appointment request. The Tracking Report [DGEN NEACL MGT RPT2] option is updated to include a new column for the date of the appointment request if the Veteran initially answered YES when completing a VA Form 10-10EZ in ES, VistA, or online. The Call List [DGEN NEACL MGT RPT1] option detailed format includes a new row to display the date of the appointment request if the Veteran initially answered YES when completing a VA Form 10-10EZ in ES, VistA, or online. The ^XINDEX issue 'Line is longer than 245 bytes' encountered in Primary Developer Review is due to a Kernel Toolkit defect, it is not due to patch DG*5.3*978. Incident INC4991239 was entered and it will be fixed in patch XT*7.3*140. Compiled list of Errors and Warnings Apr 11, 2019@10:37:33 page 1 |dd2 * * 68 Lines, 4678 Bytes, Checksum: K DIV S DIV=X,D0=DA,DIV(0)=D0 S Y(0)=X S Y(1)=$S($D(^DPT(D0,1010.15)):^ (1010.15),1:"") S X=$P(Y(1),U,13)="" I X S X=DIV S Y(1)=$S($D(^DPT(D0, 1010.15)):^(1010.15),1:"") S X=$P(Y(1),U,13),X=X S DIU=X K Y S X=DIV S X=DIV,X=X X ^DD(2,1010.1511,1,4,1.4) 1010.1511XRF4S+1 S - Line is longer than 245 bytes. Listing of Updates ================== This patch includes the following enhancements to VistA REE: 1. The Management Edit [DGEN NEACL REQUEST MGT EDIT] option is modified as follows: a. The user is prompted to enter "Does the New Enrollee want an appt. with a VA doctor/provider at [Preferred Facility]?" if the patient has not requested an appointment and if the other conditions defined below in item d are met. * BEGIN SCREEN CAPTURE * Select New Enrollee Appointment Request Management Menu <TEST ACCOUNT> Option: ED Management Edit Select PATIENT NAME: TESTPATIENT,ONE 5-21-54 ######### NO NSC VETERAN Enrollment Priority: GROUP 8c Category: ENROLLED End Date: PREFERRED FACILITY: ZZ DUP ALBANY.DOMAIN.EXT (500) APPOINTMENT REQUEST ON 1010EZ: NO Does the New Enrollee want an appt. with a VA doctor/provider at ZZ DUP ALBANY.DOMAIN.EXT (500)?: NO// * END SCREEN CAPTURE * b. If the user answers YES at this prompt, the Veteran is placed on the NEAR Call List [DGEN NEACL MGT RPT1], Call List (background job) [DGEN NEACL MGT RPT1BK] and NEAR Tracking Report [DGEN NEACL MGT RPT2] options. c. The response is stored in the APPOINTMENT REQUEST ON 1010EZ field (#1010.159) in the PATIENT File (#2). d. The conditions that result in displaying "Does the New Enrollee want an appt. with a VA doctor/provider at [Preferred Facility]?" are: i. The value of the patient's APPOINTMENT REQUEST ON 1010EZ field (#1010.159) in the PATIENT file (#2) is NULL or NO. ii. The patient's ENROLLMENT STATUS field (#.04) in the PATIENT ENROLLMENT file (#27.11) is equal to ENROLLED. iii. The VistA site is a Primary or Satellite Facility of the PREFERRED FACILITY. This is defined as the first three characters of the VistA Site number (STATION NUMBER field (#.04) in the STATION NUMBER (TIME SENSITIVE) file (#389.9)) match the first three characters of the patient's PREFERRED FACILITY field (#27.02) in the PATIENT file (#2). Otherwise the message "Site is not Patient's Preferred Facility. Preferred Facility must be updated." appears. * BEGIN SCREEN CAPTURE * Select PATIENT NAME: TESTPATIENT,ONE 1-1-47 xxxxxxxx NO NSC VETERAN Enrollment Priority: GROUP 1 Category: ENROLLED End Date: PREFERRED FACILITY: MANCHESTER (608) Site is not Patient's Preferred Facility. Preferred Facility must be updated. Select PATIENT NAME: * END SCREEN CAPTURE * * BEGIN SCREEN CAPTURE * Select PATIENT NAME: TESTPATIENT,ONE 5-21-54 ######### NO NSC VETERAN Enrollment Priority: GROUP 8c Category: ENROLLED End Date: PREFERRED FACILITY: ZZ DUP ALBANY.DOMAIN.EXT (500) APPOINTMENT REQUEST ON 1010EZ: NO Does the New Enrollee want an appt. with a VA doctor/provider at ZZ DUP ALBANY.DOMAIN.EXT (500)?: NO// NO APPOINTMENT REQUEST ON 1010EZ: NO Enter RETURN to continue: Select PATIENT NAME: * END SCREEN CAPTURE * e. If the response to "Does the New Enrollee want an appt. with a VA doctor/provider at [Preferred Facility]?" is YES, the system prompts for "Date the Appointment Request Made" and the response is stored in the APPOINTMENT REQUEST DATE field (#1010.1511) in the PATIENT file (#2). i. The date may not be in the future. ii. The user may press RETURN and is returned to the "Does the New Enrollee want an appt. with a VA doctor/provider at [Preferred Facility]?" prompt. * BEGIN SCREEN CAPTURE * Select New Enrollee Appointment Request Management Menu <TEST ACCOUNT> Option: ED Management Edit Select PATIENT NAME: TESTPATIENT,ONE 11-11-11 ######### YES SC VETERAN Enrollment Priority: GROUP 1 Category: ENROLLED End Date: PREFERRED FACILITY: ZZ DUP ALBANY.DOMAIN.EXT (500) APPOINTMENT REQUEST ON 1010EZ: NO Does the New Enrollee want an appt. with a VA doctor/provider at ZZ DUP ALBANY.DOMAIN.EXT (500)?: NO// YES Date the Appointment Request Made?: // T-30 (JAN 31, 2019) Select PATIENT NAME: * END SCREEN CAPTURE * 2. There are no changes to the Management Edit [DGEN NEACL REQUEST MGT EDIT] option if the Veteran has already requested an appointment in ES, VistA, or online. 3. The Tracking Report [DGEN NEACL MGT RPT2] option is modified. The report ("APPT.REQUEST") column now displays the appointment request date whenever the appointment was requested, including from the Management Edit [DGEN NEACL REQUEST MGT EDIT] option. The report includes a new column ("ORIGINAL APPT. REQUEST"). This column is populated with the date the user answered the appointment request question, and does not indicate the Veteran requested an appointment on that date. The Original Appointment Request Date is not used in any other reporting or calculations. a. Detail and Summary Reports have the report filter labels changed from "APPOINTMENT REQUEST ON 1010EZ START DATE" to "APPOINTMENT REQUEST START DATE" and "APPOINTMENT REQUEST ON 1010EZ END DATE" to "APPOINTMENT REQUEST END DATE". b. A new column "ORIGINAL APPT. REQUEST" is added to the Detailed Report as the 4th column and displays the ORIGINAL APPOINTMENT REQUEST DATE field (#1010.1513) in the PATIENT file (#2). The date of the Veteran's first response to the "Does the New Enrollee want an appt. with a VA doctor/provider at [Preferred Facility]?" prompt will display in this column. c. The Detailed Report layout is modified to abbreviate column headings to fit the additional column. * BEGIN SCREEN CAPTURE * Select New Enrollee Appointment Request Management Menu <TEST ACCOUNT> Option: TR Tracking Report Select one of the following: D DETAILED S SUMMARY Select report format: SUMMARY// DETAILED APPOINTMENT REQUEST START DATE: MAR 08, 2019// (MAR 08, 2019) APPOINTMENT REQUEST END DATE: MAR 15, 2019// (MAR 15, 2019) Select individual Preferred Facilities? NO// DEVICE: HOME// UCX/TELNET NEW ENROLLEE APPOINTMENT REQUEST TRACKING REPORT Date: MAR 15, 2019 ORIGINAL SCHEDULED APPT. APPT. APPT. # REQ NAME EP/CV REQUEST REQUEST DATE DAYS STA ============================ ===== ========= ========= ========= ======= ADAM(####) 8/ 03/14/19 03/14/19 03/15/19 1 F COMMENT: AutoComm:null|FILLED SMITH(####) 2/ 03/12/19 03/15/19 4 F SUMMARY ========================================================================== Total number of veteran's with CANCELLED request status 0 Total number of veteran's with EWL request status 0 Total number of veteran's with FILLED request status 2 Total number of veteran's with CONTACTED - IN PROCESS request status 0 Total number of veteran's PENDING ACTION 0 * END SCREEN CAPTURE * 4. The Call List [DGEN NEACL MGT RPT1] option and Call List (background job) [DGEN NEACL MGT RPT1BK] option are modified. The short format and detailed format reports now display the appointment request date whenever the appointment was requested, including from the Management Edit [DGEN NEACL REQUEST MGT EDIT] option. The Detailed Report now displays the date of the appointment request if the Veteran initially answered YES when completing a VA Form 10-10EZ in ES, VistA, or online. a. The Detailed Report has an additional row "ORIGINAL APPOINTMENT DATE" displaying the ORIGINAL APPT. REQUEST DATE field (#1010.1513) in the PATIENT file (#2). This row is populated with the date the user answered the appointment request question, and does not indicate the Veteran requested an appointment on that date. The Original Appointment Request Date is not used in any other reporting or calculations. b. The Detailed Report field label "1010EZ APPT. REQUEST DATE:" is changed to "APPT. REQUEST DATE:". * BEGIN SCREEN CAPTURE * Select New Enrollee Appointment Request Management Menu <TEST ACCOUNT> Option: l Call List Select one of the following: D DETAILED S SHORT Select report format: SHORT// d DETAILED Select individual Preferred Facilities? NO// DEVICE: HOME// ;;; HOME -------------------------------------------------------------- NEW ENROLLEE APPOINTMENT REQUEST CALL LIST Date: DEC 13, 2018 Page: 1 --------------------------------------------------------------- Enrollment Priority: GROUP 1 Category: ENROLLED End Date: TEST, FIRST (9999) ORIGINAL APPT. REQUEST DATE: APPT. REQUEST DATE: NOV 27, 2018 REQUEST STATUS: COMMENT: PHONE [RESIDENCE]: 99999999999 PHONE [CELLULAR]: 9999999999 PREFERRED FACILITY: CHEY6 TEST LAB(987) --------------------------------------------------------------- TEST, FOURTH (9999) Enrollment Priority: GROUP 4 Category: ENROLLED End Date: ORIGINAL APPT. REQUEST DATE: NOV 27, 2018 APPT. REQUEST DATE: NOV 27, 2018 REQUEST STATUS: COMMENT: PHONE [RESIDENCE]: (999)999-9999 PHONE [CELLULAR]: (999)999-9999 PREFERRED FACILITY: CHEY6 TEST LAB(987) --------------------------------------------------------------- SUMMARY ======================================================================= Total number of veteran's with EWL request status 0 Total number of veteran's with CONTACTED - IN PROCESS request status 0 Total number of veteran's PENDING ACTION 13 * END SCREEN CAPTURE * 5. Four new fields are added to the PATIENT file (#2) for historical purposes and NEAR List reporting: Call List [DGEN NEACL MGT RPT1], Call List (background job)[DGEN NEACL MGT RPT1BK] and Tracking Report [DGEN NEACL MGT RPT2] options: a. ORIGINAL APPOINTMENT REQUEST field (#1010.1512) b. ORIGINAL APPT REQUEST DATE field (#1010.1513) c. ORIG APPT REQUEST CHG DT/TM field (#1010.1514) d. APPT REQUEST 1010EZ CHG DT/TM field (#1010.1515) 6. The following fields in the PATIENT file (#2) are modified to turn on auditing: a. APPOINTMENT REQUEST ON 1010EZ field (#1010.159) b. APPOINTMENT REQUEST DATE field (#1010.1511) * BEGIN SCREEN CAPTURE * Select PATIENT NAME: TESTPATIENT,ONE 7-1-71 ######### NO NSC VETERAN Another one: Standard Captioned Output? Yes// (Yes) Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and Record Number (IEN) Display Audit Trail? No// YES . . <patient data is listed here> . . APPOINTMENT REQUEST DATE: Created on MAR 14, 2019@00:51:10 by User #101101 APPOINTMENT REQUEST ON 1010EZ: Changed from "NO" on MAR 14, 2019@00:51:10 by User #101101 * END SCREEN CAPTURE * 7. The ORIG APPT REQUEST CHG DT/TM field (#1010.1514) in the PATIENT file (#2) will capture the last change date/time of the appointment request or appointment request date (date/time when the ORIGINAL APPOINTMENT REQUEST field (#1010.1512) in the PATIENT file (#2) or ORIG APPT REQUEST DATE field (#1010.1513) in the PATIENT file (#2) is updated). 8. Two triggers are added to the APPOINTMENT REQUEST ON 1010EZ field (#1010.159) in the PATIENT file (#2) when the field is updated: a. The APPT REQUEST 1010EZ CHG DT/TM field (#1010.1515) in the PATIENT file (#2) will capture the date/time when APPOINTMENT REQUEST ON 1010EZ field (#1010.159) in the PATIENT file (#2) is updated. b. The ORIGINAL APPOINTMENT REQUEST field (#1010.1512) in the PATIENT file (#2) captures the value of the APPOINTMENT REQUEST ON 1010EZ field (#1010.159) in the PATIENT file (#2) the first time that value is set. 9. Two triggers are added to the APPOINTMENT REQUEST DATE field (#1010.1511) in the PATIENT file (#2) when the field is updated: a. The APPT REQUEST 1010EZ CHG DT/TM field (#1010.1515) in the PATIENT file (#2) will capture the date/time when the APPOINTMENT REQUEST DATE field (#1010.1511) in the PATIENT file (#2) is updated. b. The ORIGINAL APPT REQUEST DATE field (#1010.1513) in the PATIENT file (#2) captures the value of the APPOINTMENT REQUEST DATE field (#1010.1511) in the PATIENT file (#2) the first time that value is set. 10. The HL7 interface with ES is modified to add four additional data elements in the ZIO segment of the ORF/ORU-Z11 message. a. Sequence 7: UPDATE DATE/TIME corresponding to APPT REQUEST 1010EZ CHG DT/TM field (#1010.1515) in the PATIENT file (#2). b. Sequence 8: ORIGINAL APPOINTMENT REQUEST corresponding to ORIGINAL APPOINTMENT REQUEST field (#1010.1512) in the PATIENT file (#2). c. Sequence 9: ORIGINAL APPOINTMENT REQUEST DATE corresponding to ORIGINAL APPT REQUEST DATE field (#1010.1513) in the PATIENT file (#2). d. Sequence 10: UPDATE DATE/TIME corresponding to ORIG APPT REQUEST CHG DT/TM field (#1010.1514) in the PATIENT file (#2). Note: The ZIO segment includes sequence 5 APPOINTMENT REQUEST ON 1010EZ corresponding to the APPOINTMENT REQUEST ON 1010EZ field (#1010.159) in the PATIENT file (#2) and sequence 6 APPOINTMENT REQUEST DATE corresponding to the APPOINTMENT REQUEST DATE field (#1010.1511). 11. When VistA receives an ORF/ORU-Z11 message, the processing of these sequences is as follows: a. If the ORIGINAL APPOINTMENT REQUEST field (#1010.1512) in the PATIENT file (#2) is empty, sequences 8, 9 and 10 are stored in their corresponding fields. b. If the date/time in the APPT REQUEST 1010EZ CHG DT/TM field (#1010.1515) in the PATIENT file (#2) is more recent than the date/time in sequence 7, the data in sequences 5, 6, and 7 are not stored in VistA. c. If the APPOINTMENT REQUEST ON 1010EZ field (#1010.159) in the PATIENT file (#2) is YES and sequence 5 is NO, an Application Error (AE) is sent back to ES. d. If the APPOINTMENT REQUEST DATE in sequence 6 is a future date, an AE is sent back to ES. e. Otherwise the data in sequences 5, 6 and 7 are stored in their corresponding fields. f. If any sequence being filed contains double quotes (""), the corresponding field in VistA is deleted. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- PATIENT (#2) APPOINTMENT REQUEST Modified ON 1010EZ (#1010.159) APPOINTMENT REQUEST Modified DATE (#.1010.1511) ORIGINAL APPOINTMENT New REQUEST (#.1010.1512) ORIGINAL APPT REQUEST New DATE (#.1010.1513) ORIG APPT REQUEST New CHG DT/TM (#.1010.1514) APPT REQUEST 1010EZ New CHG DT/TM (#.1010.1515) Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- DGEN NEACL INPUT PATIENT (#2) Modified Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A Additional Information: ---------------------- Blood Bank Team Coordination: N/A New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: N/A Problem: -------- N/A Resolution: ----------- N/A Test Sites: ---------- Jesse Brown VA Medical Center (Chicago Westside, Chicago Lakeside), Chicago, IL Oklahoma City VA Medical Center, Oklahoma City, OK West Palm Beach VA Medical Center, West Palm Beach, FL Software and Documentation Retrieval Instructions: ---------------------------------------------------- Documentation describing the new functionality and/or a host file containing a build may be included in this release. The preferred method is to retrieve the files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve the files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: https://www.domain.ext/vdl Documentation Title File Name SFTP Mode ----------------------------------------------------------------------- DG_53_P978.KID Release Notes DG_5_3_P978_RN.PDF (binary) User Manual - Appointment Menu APPT.PDF (binary) Host File Name FTP Mode --------------------------------------------------------------------- DG_53_P978.KID (ASCII) Patch Installation: ------------------ Pre/Post Installation Overview: Use default answers for KIDS load/install questions. Multi-Build: http://code.osehra.org/VistA.git/blob/master/Packages/MultiBuilds/DG_53_P978.KIDs Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Income+Verification+Match/Patches/IVM_2.0_180

Patch Subject: MASTER VETERAN INDEX VISTA ENHANCEMENTS - EHRM SUPPORT Description: ============ NOTE: Master Patient Index (MPI) 'EHRM (Electronic Health Record Modernization) SUPPORT' enhancements are being distributed in four VistA namespaces: DG, MPIF, RG and XU. The only build enforced requirement is that: - DG*5.3*981 be installed before MPIF*1.0*71. **Note: Patches RG*1.0*72 and XU*8.0*710 can be installed in any order as there are NO dependencies to these other patches. (Do NOT install MPIF*1.0*71 or RG*1.0*72 on legacy sites or on the FORUM CLAIMS system) NOTE: Legacy sites and the FORUM CLAIMS system can install just the DG*5.3*981 and XU*8.0*710 patches. MPIF*1.0*71 and RG*1.0*72 should NOT be installed on legacy sites or on the FORUM CLAIMS system. DG*5.3*825, DG*5.3*863, DG*5.3*967 and DG*5.3*974 are the required builds for patch DG*5.3*981. The following enhancements exported in this patch are needed to support the transition of sites to the EHRM (CERNER) application. Enhancement #1 To ensure that TREATING FACILITY LIST (#391.91) data returned from the Remote Procedure Call (RPC) [VAFC LOCAL GETCORRESPONDINGIDS] for a patient correctly identifies the IDENTIFIER STATUS (#12) of the record, the following enhancements will be implemented: - Created a new file "EHRM MIGRATED FACILITIES" (#391.919) that will store the facilities that have migrated to/implemented the CERNER application in support of EHRM. Note: The "ACRNR" new-style cross-reference (X-REF) was created at the record level of this file to allow for a quick check to determine if a facility has migrated to/implemented CERNER. - Created a new RPC [VAFC MVI MGRTD FACILITIES UPDT] that can be called from the Master Patient Index (MPI) to remotely add, update and maintain the facilities that are currently implementing CERNER in the EHRM MIGRATED FACILITIES (#391.919) file. - Created a new routine VAFCCRNR that will be triggered by the RPC [VAFC MVI MGRTD FACILITIES UPDT] to receive a list of Station Numbers from MPI for facilities that have migrated to CERNER for maintaining the EHRM MIGRATED FACILITIES (#391.919) file with. - Finally, routine VAFCTFU2 associated with the RPC [VAFC LOCAL GETCORRESPONDINGIDS] was modified so that the returned IDENTIFIER STATUS (#12) value in the TREATING FACILITY LIST (#391.91) file is transmitted as "C" if it is currently assigned an "A" (Active) or NULL value AND the facility has migrated to/implemented CERNER. Note: Merged "H" identifier statuses will continue to be returned as denoted even if the treating facility has migrated to/implemented CERNER. Enhancement #2 To support EHRM during the creation of patients that have potential matching Department of Defense (DoD) records being returned for selection in Enterprise Registration, an additional entry labeled 'selectedIdentifier' will be transmitted in the eXtensible Markup Language (XML) explicit 'ADD' message to MPI upon creation of the patient at the site. The 'selectedIdentifier' entry will contain one of the following values below to identify the existing record that was selected from Enterprise Registration if applicable: - "" Null if no results returned or nothing selected from results. - "<EDIPI>^NI^200DOD^USDOD" (DoD's) Electronic Data Interchange Personal Identifier (EDIPI) if a DoD record was selected from the results list. - "<ICN>^NI^200M^USVHA" Integration Control Number (ICN) if any other Non-DoD record was selected from the results list. NOTE: The identifier value will be determined/created in routine DPTLK7 and then added to the XML message for transmission to the MPI in routine MPIFXMLI. Enhancement #3 In support of the Health Administration Center (HAC) and MPI integration routine VAFCQRY1 (Patient Demographics Query for building the Patient Identification (PID) Health Level Seven (HL7) segment) was updated to include the HAC local modifications in support of CH*1.3*22529. These modifications will ensure that the correct Station Number of '741MM' is used when the HAC Station Number of '741' is encountered. Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- EHRM MIGRATED FACILITIES N/A *NEW FILE (#391.919) Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------------- -------------------- VAFC MVI MGRTD FACILITIES UPDT NEW Parameter Definitions Associated: Parameter Name New/Modified/Deleted --------------------------- -------------------- N/A Additional Information: New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A Defect Tracking System Ticket(s) & Overview ------------------------------------------- N/A Test Sites: ---------- Louisville KY VAMC Sheridan WY VAMC Patch Installation: Pre/Post Installation Overview ------------------------------ There are no Pre/Post installation routine processes. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Registration/Patches/DG_5.3_981

Patch Subject: PRIMARY CARE APPOINTMENTS - NEAR LIST PROCESSING Description: ============ Patch DG*5.3*982 is being released to support the enhancements for the Enterprise Health Benefits Determination (EHBD) program that focuses on updates for the Enrollment System Modernization (ESM) Phase 2 project. Patch DG*5.3*982 is also being released in support of the Enrollment System (ES) 5.7 release. Refer to Informational Patch EAS*1*180 (Enrollment Application System) for additional details regarding the ES release. ========================================================================== IMPORTANT NOTE: ========================================================================== Deployment of patch DG*5.3*982 will be conducted using a phased approach. Facilities not involved in the New Enrollee Appointment Request Scheduling Standardization Initiative (NEAR-SSI) pilot should not install the DG*5.3*982 patch until the second wave of deployment in January 2020. Once the patch is installed, automatic removal from the NEAR is limited to primary care encounters and appointments scheduled in a primary care stop code. Training will be offered prior to the January 2020 nationwide deployment. For those sites not participating in the pilot project, additional DG namespace patches may be released in the intervening period between phase 1 and phase 2 of the pilot project. Instructions will be provided as to if those patches are approved to install out of sequence. Installation by a facility not involved with the NEAR-SSI pilot prior to January 2020 poses a risk to the accuracy and quality of the NEAR list data. Once the patch is installed, specialty care appointments will now remain on the NEAR list, and users will not have received training and education to manually disposition select specialty care appointments. This will result in inaccurate reporting and mismanagement of the NEAR list. This risk can be mitigated by a site that inadvertently installs the patch prior to January 2020 by following the instructions below: Patch DG*5.3*982 Primary Care Appointments, NEAR List Processing, modifies the Call List option and New Enrollee Appointment Request Tracking Report to indicate the New Enrollee Appointment Request (NEAR) request as "filled" when a primary care appointment is scheduled, or an encounter is completed in a clinic with a primary care stop code. Once the appointment is scheduled, or the encounter completed, the entry is automatically removed from the list and NEAR report. Scheduled appointments and completed encounters in stop codes other than the designated primary stop codes will no longer auto disposition as "filled" and be removed from the NEAR list. Staff will be required to manually disposition the NEAR in the VistA NEAR Management Menu using the Management Edit option change the status to "cancelled" in order to remove it from the list and NEAR reports. NEAR list entries manually dispositioned due to an appointment scheduled in a stop code other than primary care are dispositioned as "cancelled". Staff will enter one of the following notations in the appointment request comments free text field: - Specialty Care Appointment: SC Appt Requested - Mental Health Appointment: MH Appt Requested - Community Care Appointment: CC Appt Requested * BEGIN SCREEN CAPTURE * Select PATIENT NAME: NEWAPPT,PATIENT 5-5-50 00000232 NO NSC VETERAN Enrollment Priority: GROUP 5 Category: ENROLLED End Date: APPOINTMENT REQUEST ON 1010EZ:YES// (no editing) APPOINTMENT REQUEST DATE:JUN 27, 2019// (no editing) STATUS: IN PROCESS/VETERAN CONTACTED// (last edited: OCT 23, 2019@14:47:33) STATUS: IN PROCESS/VETERAN CONTACTED// ? Enter status of appointment request. Choose from: C CANCELLED E EWL F FILLED I IN PROCESS/VETERAN CONTACTED STATUS: IN PROCESS/VETERAN CONTACTED// C CANCELLED COMMENT: // (last edited: OCT 23, 2019@14:47:36) COMMENT: // SC Appt Requested * END SCREEN CAPTURE * National Release for the following 36 sites involved in NEAR-SSI pilot is October 29, 2019 with 4 days compliance: V01/405 - White River Junction, VT HCS V01/518 - Bedford, MA HCS V01/523 - Boston, MA HCS V01/608 - Manchester, NH HCS V01/631 - Central Western Massachusetts HCS V01/650 - Providence, RI HCS V01/689 - Connecticut HCS V02/528A5 - Canandaigua, NY HCS V02/528A8 - Albany, NY HCS V02/632 - Northport, NY HCS V04/503 - Altoona, PA HCS V04/529 - Butler, PA HCS V04/562 - Erie, PA HCS V04/595 - Lebanon, PA HCS V04/693 - Wilkes-Barre, PA HCS V06/565 - Fayetteville, NC HCS V06/637 - Asheville, NC HCS V06/652 - Richmond, VA HCS V06/659 - Salisbury, NC HCS V07/534 - Charleston, SC HCS V08/546 - Miami, FL HCS V08/548 - West Palm Beach, FL HCS V08/673 - Tampa, FL HCS V08/675 - Orlando, FL HCS V10/506 - Ann Arbor, MI HCS V10/539 - Cincinnati, OH HCS V10/553 - Detroit, MI HCS V12/556 - North Chicago, IL HCS V15/589 - Kansas City, MO HCS V15/657A4 - Poplar Bluff, MO HCS V16/564 - Fayetteville, AR HCS V17/740 - Texas Valley Coastal Bend HCS V19/436 - Montana HCS V19/623 - Muskogee, OK HCS V19/666 - Sheridan, WY HCS V21/459 - Honolulu, HI HCS The remaining sites should install this patch starting January 13, 2020 with a regular compliance of 30 days (02/12/2020). This patch will modify the New Enrollee Appointment Request (NEAR) list so that Veterans will only be removed from the NEAR list if a Primary Care Appointment type is scheduled for the Veteran. All other scheduled appointment types will not impact the NEAR list. This will help ensure that a Primary Care Appointment is scheduled for the Veteran in a timely manner. Additionally, the NEAR List Tracking report will better reflect the current scheduling status for the Veterans on the report. ========================================================================== Currently, in Veterans Health Information System and Technology Architecture (VistA) Registration, Eligibility & Enrollment (REE), the Call List option [DGEN NEACL MGT RPT1] displays newly enrolled Veterans who applied for VA Healthcare and indicated they want an appointment with a VA health care provider. VistA users can use the New Enrollee Appointment Request (NEAR) Call List (generated by the Call List option [DGEN NEACL MGT RPT1]) to view newly enrolled Veterans waiting to have appointments scheduled. This list is sometimes referred to as the local NEAR list, or local NEAR Call List. A patient remains on the local NEAR Call List until any appointment is scheduled for the patient. With patch DG*5.3*982, the Call List option [DGEN NEACL MGT RPT1] is modified to include a Veteran on the local NEAR Call List until they have been scheduled for a Primary Care Appointment. The Tracking Report option [DGEN NEACL MGT RPT2] is modified so that only Primary Care Appointments will populate the SCHEDULED APPT DATE column of the Tracking Report. An appointment or encounter is considered a Primary Care Appointment only when the clinic is configured with primary and secondary position stop codes as one of the combinations listed below. This portion of the clinic configuration is in the HOSPITAL LOCATION file (#44) STOP CODE NUMBER field (#8) and the CREDIT STOP CODE field (#2503). Primary Primary Position Secondary Secondary Position Position STOP CODE NUMBER Position CREDIT STOP CODE STOP CODE Name (#40.7,.01) CREDIT Name (#40.7,.01) NUMBER STOP CODE (#44,8) (#44,2503) ========================================================================== 322 COMP WOMEN'S HLTH 117 NURSING (2ND ONLY) 322 COMP WOMEN'S HLTH 160 CLINICAL PHARMACY 322 COMP WOMEN'S HLTH 185 NURSE PRACTIONER 322 COMP WOMEN'S HLTH 186 PHYSICIAN ASSISTANT 322 COMP WOMEN'S HLTH 187 CLINICAL NURSE SPECIALIST 322 COMP WOMEN'S HLTH 188 FELLOW/RESIDENT 322 COMP WOMEN'S HLTH Null 323 PRIMARY CARE/MEDICINE 117 NURSING (2ND ONLY) 323 PRIMARY CARE/MEDICINE 160 CLINICAL PHARMACY 323 PRIMARY CARE/MEDICINE 185 NURSE PRACTIONER 323 PRIMARY CARE/MEDICINE 186 PHYSICIAN ASSISTANT 323 PRIMARY CARE/MEDICINE 187 CLINICAL NURSE SPECIALIST 323 PRIMARY CARE/MEDICINE 188 FELLOW/RESIDENT 323 PRIMARY CARE/MEDICINE Null 348 PRIMARY CARE SHARED APPT 117 NURSING (2ND ONLY) 348 PRIMARY CARE SHARED APPT 160 CLINICAL PHARMACY 348 PRIMARY CARE SHARED APPT 185 NURSE PRACTIONER 348 PRIMARY CARE SHARED APPT 186 PHYSICIAN ASSISTANT 348 PRIMARY CARE SHARED APPT 187 CLINICAL NURSE SPECIALIST 348 PRIMARY CARE SHARED APPT 188 FELLOW/RESIDENT 348 PRIMARY CARE SHARED APPT Null 350 GERIPACT 117 NURSING (2ND ONLY) 350 GERIPACT 160 CLINICAL PHARMACY 350 GERIPACT 185 NURSE PRACTIONER 350 GERIPACT 186 PHYSICIAN ASSISTANT 350 GERIPACT 187 CLINICAL NURSE SPECIALIST 350 GERIPACT 188 FELLOW/RESIDENT 350 GERIPACT Null 160 CLINICAL PHARMACY 322 COMP WOMEN'S HLTH 160 CLINICAL PHARMACY 323 PRIMARY CARE/MEDICINE 210 SPINAL CORD INJURY (SCI) 322 COMP WOMEN'S HLTH 210 SPINAL CORD INJURY (SCI) 323 PRIMARY CARE/MEDICINE 310 INFECTIOUS DISEASE 322 COMP WOMEN'S HLTH 310 INFECTIOUS DISEASE 323 PRIMARY CARE/MEDICINE 313 RENAL/NEPHROL(EXCEPT DIALYSIS) 322 COMP WOMEN'S HLTH 313 RENAL/NEPHROL(EXCEPT DIALYSIS) 323 PRIMARY CARE/MEDICINE The Management Edit [DGEN NEACL REQUEST MGT EDIT] option displays the informational message "The Veteran has been removed from the NEAR Call List." when the user sets the Appointment Request Status to FILLED: * BEGIN SCREEN CAPTURE * Select PATIENT NAME: PRIMARYAPPT,SECOND MD 2-29-92 666329876 NO SC VETERAN Enrollment Priority: GROUP 5 Category: ENROLLED End Date: APPOINTMENT REQUEST ON 1010EZ:YES// (no editing) APPOINTMENT REQUEST DATE:APR 10, 2019// (no editing) STATUS: F FILLED The Veteran has been removed from the NEAR Call List. COMMENT: * END SCREEN CAPTURE * Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File Number New/Modified/Deleted --------- ----------- -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- DGEN NEACL INPUT PATIENT (#2) Modified Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A Additional Information: ----------------------- N/A Blood Bank Team Coordination: ----------------------------- N/A New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: N/A Test Sites: ----------- Durham VA Medical Center, Durham, NC West Palm VA Medical Center, West Palm Beach, FL Software and Documentation Retrieval Instructions: -------------------------------------------------- This software is being released as a patch (PackMan) message. Documentation describing the new functionality is included in this release. The preferred method is to retrieve the files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve the files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/ Documentation Title File Name FTP Mode --------------------------------------------------------------------- DG*5.3*982 Release Notes DG_5_3_982_RN.PDF (binary) DG*5.3*982 Deployment, Installation, Back-out, and Rollback Guide DG_5_3_982_DIBRG.PDF (binary) User Manual - Appointment Menu APPT.PDF (binary) PIMS Technical Manual PIMSTM.PDF (binary) Host File Name FTP Mode --------------------------------------------------------------------- N/A Patch Installation: ------------------- Pre/Post Installation Overview: ------------------------------- Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Registration/Patches/DG_5.3_982

Patch Subject: MASTER VETERAN INDEX VISTA ISSUE - INPATIENT NAME UPDATES Description: ============ NOTE: To prevent legacy systems ending up as Treating Facilities, RG* and MPIF* patches should NOT be installed on legacy systems or the FORUM CLAIMS system (since it is NOT a Veterans Affair Medical Center (VAMC) VistA system). RG*1.0*71 is the ONLY required build for patch RG*1.0*72. NOTE: Master Patient Index (MPI) 'EHRM (Electronic Health Record Modernization) SUPPORT' enhancements are being distributed in four VistA namespaces: DG, MPIF, RG and XU. The only build enforced requirement is that: - DG*5.3*981 be installed before MPIF*1.0*71. **Note: Patches RG*1.0*72 and XU*8.0*710 can be installed in any order as there are NO dependencies to these other patches. (Do NOT install MPIF*1.0*71 or RG*1.0*72 on legacy sites or on the FORUM CLAIMS system) NOTE: Legacy sites and the FORUM CLAIMS system can install just the DG*5.3*981 and XU*8.0*710 patches. MPIF*1.0*71 and RG*1.0*72 should NOT be installed on legacy sites or on the FORUM CLAIMS system. The following issue exported in this patch was discovered by the Healthcare Identity Management (HC IdM) business office and will address ticket INC7125871 where an admitted patient name can be inadvertently updated when the Master Veteran Index (MVI) does a Primary View (PV) sync out to sites on a Name Update. Issue When patch RG*1.0*71 was released to support the collection of the patient's legal name which can exceed 30-characters, a reference for determining which name field to look at in routine RGADTP2 was overlooked, resulting in name changes being inadvertently allowed for patients who had been admitted. Therefore, routine RGADTP2 was modified to look at the NAME COMPONENTS (#1.01) field instead of the NAME (#.01) field in the PATIENT (#2) file to prevent name updates from being processed when the patient has been admitted. Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted --------------------------- -------------------- N/A Additional Information: New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A Defect Tracking System Ticket(s) & Overview ------------------------------------------- INC7125871 - Inpatient Updated Problem: -------- Upon release of patch RG*1.0*71 to support the collection of the patient's legal name in the Veteran Affairs (VA) Master Person Index (MPI) by storing them in the NAME COMPONENTS (#20) file, a section of code was overlooked that specified what field to look at when processing the patient update (A08) Health Level Seven (HL7) messages resulting in name updates occurring for admitted patients (ie. Inpatients). Note: Patient's Legal Name may exceed the VistA maximum of 30-characters in the NAME (#.01) field of the PATIENT (#2) file. Resolution: ----------- Routine RGADTP2 was modified to look at the NAME COMPONENTS (#1.01) field instead of the NAME (#.01) field in the PATIENT (#2) file to determine whether a patient name update occurred to prevent the patient's name from being updated when the patient has been admitted. Test Sites: ---------- Louisville KY VAMC Sheridan WY VAMC Patch Installation: Pre/Post Installation Overview ------------------------------ There are no Pre/Post installation routine processes. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Clinical+Information+Resource+Network/Patches/RG_1.0_72

Patch Subject: KERNEL VISTA ENHANCEMENTS - EHRM SUPPORT Description: ============ XU*8.0*343 and XU*8.0*711 are the required builds for patch XU*8.0*710. The following enhancements exported in this patch are in support of the Electronic Health Record Modernization (EHRM) that the Master Veteran Index (MVI) team has implemented to assist with the transition as sites move to the CERNER application. The enhancements listed below work in conjunction with the MVI changes that have been exported in patch MPI*1.0*129. Enhancement #1 A new restricted Remote Procedure Call (RPC) [XUS MVI NEW PERSON BULK GET] has been created to allow the MVI system to remotely retrieve delimited attribute information for 'ACTIVE' record entries from the NEW PERSON (#200) file. MVI will then export these returned results for a specific site to a flat file, which will then be imported by the Person Service Identity Management (PSIM) system so that the entries can be evaluated further. NEW PERSON Attributes: --------------------- - Internal Entry Number - NAME (#.01) - Address STREET ADDRESS 1 (#.111) STREET ADDRESS 2 (#.112) STREET ADDRESS 3 (#.113) CITY (#.114) STATE (#.115) ZIP CODE (#.116) - OFFICE PHONE (#.132) - EMAIL ADDRESS (#.151) - SEX (#4) - DOB (#5) - SSN (#9) - NAME COMPONENTS (#10.1) [*Pointer to NAME COMPONENTS (#20) file] FAMILY (LAST) NAME (#1) GIVEN (FIRST) NAME (#2) MIDDLE NAME (#3) PREFIX (#4) SUFFIX (#5) DEGREE (#6) - DIVISION (#16) [*Multiple entries possible] - NPI (#41.99) - KEYS (#51) [*Multiple entries possible] - DEA# (#53.2) - PRIMARY MENU OPTION (#201) - SECONDARY MENU OPTIONS (#203) [*Multiple entries possible] - SUBJECT ORGANIZATION (#205.2) - SUBJECT ORGANIZATION ID (#205.3) - UNIQUE USER ID (#205.4) - NETWORK USERNAME (#501.1) - DEA EXPIRATION DATE (#747.44) Note: NEW PERSON (#200) file records are determined to be 'ACTIVE' for this RPC when the following 3 statements are ALL verified as 'TRUE': 1. NOT Disuser'd 2. NOT Terminated 3. Has a Primary Menu Option assigned Enhancement #2 The existing RPC [XUS MVI NEW PERSON UPDATE] and corresponding routine XUMVINPU have been modified to allow the NPI (National Provider Identifier) field (#41.99) in the NEW PERSON (#200) file to be updated remotely by MVI for a specific user entry. In addition, the FileMan (FM) filer call FILE^DIE in routine XUMVINPU has been modified to set the optional 'FLAGS' property to "E", to ensure that values entered are validated through the field Input Transforms if they exist. Issue #1 To ensure that both 'Active' and 'Visitor' NEW PERSON (#200) file records are counted independently when the [XUS MVI NEW PERSON DATA] RPC is called by MVI, routine XUMVIDTA was modified to remove the QUIT statement after the 'Visitor' record has been tallied to allow other additional counts (ie. 'Active') to be processed if they apply, as it is possible to have both an 'Active' and 'Visitor' entry at sites. Issue #2 Upon release of patch XU*8.0*343, the Name Standardization process in routine XLFNAME2 was modified and introduced an unknown defect where the maximum length of the source field being edited was replaced with a hard-coded value of 35, which has allowed for the creation/storage of names in the PATIENT file (#2) that are greater than the data definition of 30-characters. Therefore, routine XLFNAME2 was updated to revert back to using the data defined length of the source field or the passed in character limit as long as it doesn't exceed the data defined length, instead of the hard-coded 35-character limit. Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------------- -------------------- XUS MVI NEW PERSON BULK GET NEW XUS MVI NEW PERSON UPDATE MODIFIED Parameter Definitions Associated: Parameter Name New/Modified/Deleted --------------------------- -------------------- N/A Additional Information: Blood Bank Team Coordination ---------------------------- EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch XU*8.0*710 contains changes to a package referenced in ProPath standard titled: BBM Team Review of VistA Patches. This patch does not alter or modify any VistA Blood Bank software design safeguards or safety critical elements functions. RISK ANALYSIS: Changes made by patch XU*8.0*710 have no adverse effect on Blood Bank software functionality, therefore RISK is none. New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A Defect Tracking System Ticket(s) & Overview ------------------------------------------- INC6745453 - Emergency Department Information System (EDIS) Name Component Issue Problem: -------- When the name fields in the NAME COMPONENTS file (#20) are edited, it is possible that the full name built from those components could exceed 30 characters in length, and up to 35 characters could then be stored in the NAME field (#.01) of the PATIENT file (#2) even though the data definition of that field only allows for a maximum of 30-characters. This is due to an issue in the Name Standardization process that was updated and released in patch XU*8.0*343 when the field length was set to a hard-coded value of 35-characters. Note: The Name Standardization process also updates the NEW PERSON file (#200), but the NAME (#.01) value there allows for 35-characters to be entered. Resolution: ----------- Routine XLFNAME2 was modified to revert back to using the data defined length of the source field being updated or the routine parameter that is passed in defining the requested character limit to use as long as it doesn't exceed the data defined length, else the data defined length of the source field will be used in determining how many characters to store in the field. Test Sites: ---------- Louisville KY VAMC Sheridan WY VAMC Patch Installation: Pre/Post Installation Overview ------------------------------ There are no pre/post installation routines processes. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Kernel/Patches/XU_8.0_710

Patch Subject: ABNORMAL REPORT FORMATTING & DX CODE PROCESSING Description: ============ Associated Ticket(s): ===================== INC4644465 INC4753897 INC2890615 INC6714227 Associated NSR(s): ================== N/A Participating Test Sites: ========================= White River Junction VAMC South Texas HCS (San Antonio) Problem A: ---------- The Abnormal Exam Report [RA ABNORMAL] is formatted in a way that is sometimes misleading as to which diagnostic codes go with which exams. Resolution A: ------------- Routine RAPRINT1 is modified to adjust the report formatting so that the diagnostic code header is clearly positioned above the exams it represents. Problem B: ---------- A subscript error was reported when attempting to process a "Procedure Changed" alert [#67] in CPRS: <SUBSCRIPT>SET1+25^RAO7PC4 The 'changed from' procedure is missing from the 'DATA FOR PROCESSING' field [#2] in the ALERT TRACKING [#8992.1] file. RESOLUTION B: ------------- Routine RAO7PC4 is modified as follows: If the 'changed from' procedure is missing in the alert data, it will first try to get the procedure information from the order, if available, and if that fails it will display an 'UNKNOWN' on the alert when processed. PROBLEM C: ---------- Radiology identifies the primary and secondary diagnostic codes (DX) based on the order they are received in the OBX segments of the report message (HL7 version 2.4 only). A primary designation on Powerscribe does not dictate the order that they are sent, but instead they are sorted by the DX code's number (highest to lowest). So, a secondary code number of 1200 (AAA Not Present) will be above the primary code of 1000 (no alert required) and therefore be filed as Primary in Radiology. RESOLUTION C: ------------- Voice Recognition sends the Primary designation along with the DX code. VistA Radiology will check for that designation and assign the code as Primary regardless of its position in the HL7 message. If no Primary designation is sent, the first code will still be identified as Primary. PROBLEM D: ---------- The radiology registration menu enforces a location switch to the modality of the ordered procedure. There are times when it is necessary to register an exam under a different modality than what was ordered, as decided by the radiologist at the time of the procedure. Currently, the package prevents the modality from being changed and the order must be discontinued and reordered. RESOLUTION D: ------------- A new security key (RA SWITCHLOC) is distributed with this patch. Holders of this key will be able to register an exam under a different modality than the ordered procedure when appropriate. Routine RAREG3 is modified to check for this security key at the time of exam registration. DOCUMENTATION RETRIEVAL: ======================== These are the documentation changes associated with this patch: Radiology/Nuclear Medicine Technical Manual These manuals are available on the ANONYMOUS.SOFTWARE directory at one of the following Office of Information (OI) Field Offices. These files should be retrieved in binary format. Sites may retrieve documentation as follows: The preferred method is to SFTP the files from download.vista.domain.ext, which will transmit the files from the first available FTP server. The documentation distribution includes: File Name Description Protocol --------- ----------- -------- RA5_0TM.DOCX Technical Manual BINARY Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Radiology+Nuclear+Medicine/Patches/RA_5.0_157

Patch Subject: Tele Health Scheduling Enhancements Description: ============ *** IMPORTANT NOTE *** ************************************************************************** * Emergency Patches SD*5.3*704 and OR*3.0*496 will be released * * 09/13/2019. Production testing of these patches along with the * * Tele Health Management Platform (TMP) application will be conducted * * on 09/15/2019 by the following test sites: Fargo, Minneapolis and * * Boise. * * * * A Go/No Go decision will be made on 09/15/2019 by the project * * management team and communicated to the Regional Patch install teams * * no later than 09/15/2019 via the Forum Patch Messaging system via the * * G.Patch Mail Group. * * * * Do not install these patches until notified to do so. * * * ************************************************************************** Tele Health Management Platform (TMP) is implementing processes that will keep Veterans Health Information Systems and Technology Architecture (VistA) clinic and appointment data for tele health clinics and appointments in sync with the TMP application. These real time updates are triggered when appointments are made or cancelled in a clinic that has a stop code or credit stop code that is associated with tele health. Real-time clinic updates are triggered when a new tele health clinic is added at a medical center or if the stop code, credit stop code, clinic name, treating specialty, service, or overbooks allowed fields are edited. A real-time clinic update is also triggered if a tele health clinic is inactivated or if an inactive tele health clinic is reactivated. Tele health clinics are identified by stop code or credit stop codes. The current Get Consults (ORQQCN LIST) Remote Procedure Call (RPC) doesn't return the Clinically Indicated Date (CID) when the consults are returned to the calling application. TMP is replacing the call to the RPC with an HL7 query/response message. The new process returns a list of the patient's consults over the last two years and includes the CID field with the data if it is available. Displaying the CID with the consult in TMP provides the scheduler with the information needed to schedule an appointment for the consults within the 30 day window after the CID. If end users/customers need TMP technical support during Go Live or anytime thereafter, they can reach out to the National Telehealth Technology Help Desk (NTTHD) at 866-651-3180 or via email at [email protected]. Patch Components: ----------------- Bulletins: --------- N/A Files & Fields Associated: -------------------------- TMP is adding two new indices to the PATIENT File (#2), the APPOINTMENT Multiple field (#2.98). These new indices will trigger an update to be sent to TMP when an appointment is made or cancelled. TMP is adding one new index on the HOSPITAL LOCATION File (#44) on the fields list below. This new index triggers an update to TMP when one or more of these fields are edited. These new indices are installed with a post install routine. File Name(#), Sub-File Name (#) Field Numbers New/Modified/Deleted ------------------ ------------------- -------------------- PATIENT (#2), APPOINTMENT (#2.98) .01 New Index: AX298 3 New Index: AY298 SD TELE HEALTH STOP CODE FILE (#40.6) New File HOSPITAL LOCATION (#44) .01,8,2503,9.5,9,16, 1918,2505,2506 New Index: ATMP1 Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- EDIT TELE HEALTH STOP CODES run routine NEW [SD EDIT TELE HEALTH STOP CODES] Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- SD IFS EVENT DRIVER NEW SD IFS SUBSCRIBER NEW SD TMP RECEIVE CANCEL INTRA NEW SD TMP RECEIVE INTRAFACILITY NEW SD TMP S12 CLIENT SUBSCRIBER NEW SD TMP S12 SERVER EVENT DRIVER NEW SD TMP S15 CLIENT SUBSCRIBER NEW SD TMP S15 SERVER EVENT DRIVER NEW SD TMP SEND CANCEL INTRA NEW SD TMP SEND INTRAFACILITY NEW SD TMP SIU-12 SERVER NEW SD TMP SIU-S12 CLIENT NEW TMP QBP-Q13 Event Driver NEW TMP QBP-Q13 Subscriber NEW TMP RTB-K13 Event Driver NEW TMP RTB-K13 Subscriber NEW HL7 Application Parameters: Parameter Name: --------------- SD TMP APPT RECEIVE SD TMP APPT SEND SD TMP IFS RECEIVE SD TMP IFS SEND SD TMP RECEIVE CANCEL INTRA SD TMP RECEIVE INTRAFACILITY SD TMP SEND CANCEL INTRA SD TMP SEND INTRAFACILITY SD-TMP-IN SD-TMP-OUT TMP GET CONSULTS TMP SEND CONSULTS TMP VIMT TMP_OUT HLO APPLICATION REGISTRY: Registry Name: -------------- TMP_VIMT TMP_OUT HL LOGICAL LINKS: TMP adds a new link to connect to the TMP HealthShare server. HL LOGICAL LINK: ---------------- TMP_SEND Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: N/A New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- N/A Problem: -------- N/A Resolution: ----------- N/A Test Sites: ---------- Fargo, ND Minneapolis, MN Boise, ID Documentation Retrieval Instructions ------------------------------------ Software is being released as a PackMan build and/or documentation describing the new functionality introduced by this patch. The following technical documentation with known issues can be retrieved from the VA Software Document Library (VDL): TMP Release Notes D365 v4.6 The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/ Title File Name Transfer Mode -------------------------------------------------------------------------- TMP Release Notes D365 v4.6 TMP_4.6_rn.doc Binary Patch Installation: ------------------ Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Scheduling/Patches/SD_5.3_704

Patch Subject: STATEMENT SCHEDULE UPDATE Description: ============ Patch Components: ----------------- This Accounts Receivable (AR) patch supports changes to the Veterans Health Information System and Technology Architecture (VistA) to support the Patient Statement Enhancements Project (PSE). *** *** QUEUEING OF THIS PATCH HAS BEEN DISABLED *** *** SELECTED SITES MUST INSTALL ON SPECIFIC DAYS. *** Upon the first installation of this patch in a production account, *** an environment check will ensure that the patch is only installed *** on allowed days. The allowable days depends on which site you are. *** *** If your site is not listed in the chart below you can install on *** any day of the month. If your site is listed in the chart below, *** allowable days to install in production are as follows: *** *** Sites listed in the chart below may install the patch on the *** 1st of the month through the 16th of the month (inclusive). *** In addition, the 29th through the last day of the month (inclusive) *** are also valid install days. *** *** For example, if your site is listed in the chart below, *** October 1st through October 16th are valid install days. In addition, *** October 29th through October 31st are also valid install days. *** This patch updates the STATEMENT DAY field (#340,.03) that point to entries in the PATIENT file (#2). The patch also updates the SITE STATEMENT DAY field (#342,.11). The existing values for those fields are being modified to be a different day of the month for sixteen (16) Veterans Administration sites. If your site is not listed below then the patch will install but will not make any modifications to your system. Current New Site VAMC Date Date ---- --------------------- ------- ---- 438 SIOUX FALLS VA HCS 21 26 501 ALBUQUERQUE, NEW MEXICO HCS 21 26 504 AMARILLO HCS 21 26 542 COATESVILLE VAMC 21 26 562 ERIE VAMC 21 26 568 FORT MEADE, BLACK HILLS HCS 21 26 649 PRESCOTT, NORTHERN ARIZONA HCS 21 26 656 SAINT CLOUD VA HCS 21 26 688 WASHINGTON 21 26 756 EL PASO VA HCS 21 26 664 SAN DIEGO HCS 22 28 565 FAYETTEVILLE NC VAMC 22 28 658 SALEM VAMC 22 28 671 SAN ANTONIO, SOUTH TEXAS HCS 22 28 740 TEXAS VALLEY COASTAL BEND HCS 22 28 621 MOUNTAIN HOME VAMC 22 28 Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. N/A Problem: ------- N/A Resolution: ---------- N/A Test Sites: ---------- Erie, PA Richmond, VA Fayetteville, NC Software and Documentation Retrieval Instructions: ---------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/ Title File Name FTP Mode ----------------------------------------------------------------------- Deployment, Installation, PRCA_4_5_P355_IG.pdf BINARY Back-out, and Rollback Guide (PRCA*4.5*355) Patch Installation: Pre/Post Installation Overview: ------------------------------- All modifications made in this patch will be addressed by the post-install routine. See above for an explanation of what is being modified. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Accounts+Receivable/Patches/PRCA_4.5_355

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update ZISHGUX.m #2

Update ZISHGUX.m #2

ksbhaskar commented Jan 29, 2015

Update ZISHGUX.m #2

Are you sure you want to change the base?

Update ZISHGUX.m #2

Conversation

ksbhaskar commented Jan 29, 2015