Update ZISHGUX.m by ksbhaskar · Pull Request #2 · WorldVistA/VistA-M

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 anonymous@download.vista.domain.ext from the COMMAND prompt (example: sftp anonymous@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: When using Attachmate Reflection (Secure Shell): Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext When using the COMMAND prompt (example: sftp anonymous@domain.ext): Albany: anonymous@domain.ext Hines: anonymous@domain.ext Salt Lake City: anonymous@domain.ext 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: 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: Reasonable Charges V3.21 Description: ============ Implementation of Reasonable Charges v3.21 is a two-step process: 1. Installation of this patch will inactivate Reasonable Charges v3.19 charges with an inactive date of 12/31/16. (See Installation Instructions.) Patch will also update 13 billing regions with the Provider Based for Outpatient Care (type 2) to match in the primary division of host files. PLEASE NOTE FOR THE 13 SITES LISTED BELOW: There will be no charge appearing for old claims when the patch is installed. Site user must complete bills before the install, or change the type back and complete it after the install (see issue description #2 below). 2. Uploading the Reasonable Charges v3.21 charges. This will load new charges with an effective date of 01/01/17 and needs to be done immediately after the patch install. PLEASE NOTE: If possible, it is recommended that you install the LEXICON UTILITY patch LEX*2.0*109 - Code Set FY17 2nd Qtr Update before installation of IB*2.0*584. ************************************************************************** Reasonable Charges version 3.21 is a charge update to the existing Reasonable Charges billed to Third Party Payers. The primary update with this patch is to the charges, which will be implemented when the new RC v3.21 charges are uploaded (step 2). Inactive Date of Reasonable Charges v3.19 is 12/31/2016. Effective Date of Revised Reasonable Charges v3.21 is 01/01/2017. Reasonable Charges v3.19 loaded on your system will be inactivated with an inactivate date of 12/31/2016 when this patch is installed. Reasonable Charges v3.21 with an effective date of 01/01/17 will be activated on your system when the charges are uploaded as described below. ASSOCIATED TICKET: ================== 1. R11428275FY17 RC v3.21 Outpatient Reasonable Charges for 2017 2. R12055122FY17 13 Station Additions v3.21 ASSOCIATED NSR(s): ================== N/A PARTICIPATING TEST SITES: ========================= Pittsburgh HCS Upstate NY - VISN02 OVERVIEW: ========= 1. R11428275FY17 RC v3.21 Outpatient Reasonable Charges for 2017 Problem: -------- Changes in the national CPT rates need to be distributed to all hospitals so that proper billing can take place. Resolution: ----------- This patch updates the Reasonable Charges files and distributes them with a new version number and a new effective date. Routines: IBCRHBRV, IBYP584 2. R12055122FY17 13 Station Additions v3.21 Problem: -------- The CBO has requested the billing region update for the following 13 stations whose facility type has changed from Non-Provider Based (type 3) to Provider Based (type 2) in the primary division of host files v3.21. 402QB 436GJ 568HA 573GN 573QJ 626GJ 626GN 631QA 652GB 655QB 658GA 659BZ 671GC Resolution: ----------- This patch updates 13 billing regions to match the facility type 2 in the primary division of host files. Routines: IBYP584, IBYP584A Technical Description ===================== The patch exports 3 routines, two of which are the post-init (IBYP584 and IBYP584A). The post-init will inactivate all existing Reasonable Charges defined in the Charge Master. Reasonable Charges v3.19 will be inactivated with an inactive date of 12/31/16 when this patch is installed. The post-init will also update 13 billing regions with the facility type 2 to match the primary division of host files. The following is an example of the post-init portion of the installation: Reasonable Charges v3.21 Post-Install ..... >> Inactivating Existing Reasonable Charges, Please Wait... Done. 277574 existing charges inactivated >> Updating Billing Regions with Provider Based (Facility Type 2) RC 568HA - NEWCASTLE, WY Done. 1 facility type of billing regions changed Reasonable Charges v3.21 Post-Install Complete Note: The actual number of charges inactivated and facility type of billing regions changed will vary based on the number of divisions billed at your site. This will also determine the time required for the installation. 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_584

Patch Subject: NON-VA CARE THIRD-PARTY REVENUE ENHANCEMENTS Description: ============ IMPORTANT INSTALLATION NOTE: ---------------------------- There are three patches associated with this project - PRCA*4.5*310, IB*2.0*554 and FB*3.5*163. All three patches are to be installed as Packman files. There is no bundle. The three patches incorporated code from the following concurrent development and, as such, the following patches MUST be installed prior to this project: 1.) IB*2.0*528 2.) IB*2.0*530 (and associated patches PRCA*4.5*303 - BUNDLED, IB*2.0*529 and PRCA*4.5*304 - STANDALONE) 3.) FB*3.5*154 (and associated FBCS patch DSIF*3.2*38) 4.) FB*3.5*166 The three patches for this project MUST be installed in this order: 1.) PRCA*4.5*310 2.) IB*2.0*554 3.) FB*3.5*163 Description ----------- The Chief Business Office (CBO) is requesting system enhancements to The Veterans Health Information Systems and Technology Architecture (VistA) Integrated Billing (IB), Accounts Receivable (AR), and Fee Basis (FB) software modules that would allow segregating all billing and collection activities for Non-Department of Veterans Affairs (Non-VA) Care Third Party Insurance carriers' reimbursement. Current Medical Care Collections Fund (MCCF) Third Party billing and collections applications in the VistA information system do not segregate the Non-VA care claims from those claims for service rendered at Veterans Health Administration (VHA) healthcare facilities. This makes it difficult to determine whether all monies due VA for Non-VA care services are being billed and collected from Third Party insurance carriers, where applicable. The current process is a resource intensive, manual process with no assurance that all applicable Non-VA charges have been billed and collected. This project will improve the transfer of data from VistA Fee to Integrated Billing. It will record Non-VA revenue in a new fund 5287-13 to allow separate tracking of these revenues. A new third party rate type Fee Reimbursable Insurance has been created to associate the revenues to the new fund. The patch makes the following changes and enhancements: A new Copays on Hold List Manager screen will display the copays that are on hold based on the filters selected by the user. This will ease processing copays on hold. Functionality has also been added to release a copay when the patient does not have billable insurance as well as a copay on hold when the buffer file entry has been processed. The Third Party Follow Up and Trend reports have been modified to display the new rate type. Concurrent Development / Dependencies: -------------------------------------- Patch IB*2.0*554 is dependent upon enhancements in FB*3.5*154 (Separation of Duties). FB*3.5*154 is being released with DSIF*3.2*38 (Separation of Duties), DSIF*3.2*50 (AMC Defect Repair) and FB*3.5*172 (Security Keys for Separation of Duties). There was coordination with the following patches, whereby code from the following patches was incorporated into IB*2.0*554. The following patches must be installed prior to IB*2.0*554: IB*2.0*528 (^IBCNBAR, ^IBCNSM) IB*2.0*530 (^IBJDF11) Patch Components: ----------------- Files & Fields Associated: (Note: This file will not be populated with data for National Release.) File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- IB-FB INTERFACE TRACKING file (#360) New ENTRY NUMBER (#.01) PATIENT (#.02) FB AUTHORIZATION (#.03) AUTH DELETION DATE/TIME (#.04) INITIAL TREATMENT DATE (#.05) CLAIMS TRACKING ENTRY NUMBER (#1.01) BILL/CLAIMS (#1.02) INVOICE NUMBER (#1.03) INTEGRATED BILLING ACTION (#1.04) IV QUEUE (#2.01) UR QUEUE (#2.02) FR QUEUE (#2.03) SC QUEUE (#2.04) BI QUEUE (#2.05) NEXT REVIEW DT (#3.01) 1ST OR 3RD PTY (#3.02) LOG (#4) DATE/TIME (#.01) EVENT (#.02) USER (#.03) Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- IB MT ON HOLD MENU MENU MODIFIED IB OUTPUT HELD CHARGES LM ROUTINE NEW Protocols Associated: (Note: Not all Protocols will be enabled with National Release.) Protocol Name New/Modified/Deleted ------------- -------------------- IB BILLING WORKLIST ACTION MENU NEW IB BILLING WORKLIST ACTIONS NEW IB BILLING WORKLIST CLAIMS TRACKING LINK NEW IB BILLING WORKLIST COMPLETE NEW IB BILLING WORKLIST EXPAND NEW IB BILLING WORKLIST EXPAND MENU PROTOCOL NEW IB BILLING WORKLIST EXPAND REFRESH NEW IB BILLING WORKLIST HISTORY NEW IB BILLING WORKLIST INSURANCE LINK NEW IB BILLING WORKLIST MENU NEW IB BILLING WORKLIST REFRESH NEW IB BILLING WORKLIST REMOVE NEW IB NVC PRECERT WORKLIST IVACTION MENU NEW IB NVC PRECERT WORKLIST IVPRECERT NEW IB NVC PRECERT WORKLIST IVREMOVE NEW IB NVC PRECERT WORKLIST RURACTION MENU NEW IB NVC PRECERT WORKLIST RURCOMP NEW IB NVC PRECERT WORKLIST RURNRD NEW IB NVC PRECERT WORKLIST RURREMOVE NEW IBOH EXPAND HELD CHARGES NEW IBOH EXPORT TO FILE NEW IBOH HELD CHARGES ACCOUNT PROFILE NEW IBOH HELD CHARGES CLAIM TRACKING NEW IBOH HELD CHARGES PATIENT INSURANCE NEW IBOH HELD CHARGES TPJI NEW IBOH HELD CHARGES WORKLIST MENU NEW IBOH PRINT HELD CHARGES RPT NEW IBOH RELEASE HELD CHARGES NEW Templates Associated: (Note: Not all Templates will be enabled with National Release.) Template Name Type File Name (Number) New/Mod/Del ------------- ---- ------------------ ----------- IB SCREEN102 INPUT BILL/CLAIMS (#399) M IB BILLING WORKLIST LIST IB-FB INTERFACE TRACKING (#360) N IB BILLING WORKLIST ACTIONS LIST IB-FB INTERFACE TRACKING (#360) N IB BILLING WORKLIST EXPAND LIST IB-FB INTERFACE TRACKING (#360) N IB BILLING WORKLIST HISTORY LIST IB-FB INTERFACE TRACKING (#360) NIB NVC PRECERT WORKLIST LIST IB-FB INTERFACE TRACKING (#360) NIB NVC PRECERT WORKLIST IV LIST IB-FB INTERFACE TRACKING (#360) N IB NVC PRECERT WORKLIST RUR LIST IB-FB INTERFACE TRACKING (#360) N IBOH HELD CHARGES EXPAND LIST INTEGRATED BILLING ACTION (#350) N IBOH HELD CHARGES LIST LIST INTEGRATED BILLING ACTION (#350) N New Service Requests (NSRs): ---------------------------- 20080918 - Third Party Billing Improvements for Fee Care 20081010 - 3rd Party Billing (IB) Precertification Enhancements 20110303 - Fee-Revenue Enhancements 20110304 - Fee-Revenue SC Decision Change 20120204 - Copays on Hold - Medicare/No Insurance Patient Safety Issues (PSIs): ------------------------------ N/A Remedy Ticket(s) & Overviews: ----------------------------- N/A Test Sites: ---------- Omaha - Central Plains St. Cloud 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 Transfer Mode ------------------------------------------------------------------ Installation Guide ib_2_0_554_ig.pdf Binary Release Notes ib_2_0_554_rn.pdf Binary User Manual ib_2_0_554_um.pdf Binary Patch Installation: Pre/Post Installation Overview: ------------------------------- The post installation routine, IB20P554 is not automatically deleted as part of the installation process. You may delete it after installation if you desire. 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_554

Patch Subject: NATIVE DOMAIN STANDARDIZATION RADIOLOGY REPORTS Description: ============ The Department of Veterans Affairs (VA) Interagency Program Office (IPO) and the Department of Defense (DoD) is tasked by its charter with leading the Departments' efforts "to implement national health data standards for interoperability and [be] responsible for establishing, monitoring, and approving the clinical and technical standards profile and processes to ensure a seamless [exchange] of health data." This task of Native Domain standardization is aligned with achieving the goals outlined in the 2014 National Defense Authorization Act (NDAA) requiring that the Departments' "healthcare data [are] computable in real-time and [comply] with existing national data standards" and that the "data [are] standardized as national standards continue to evolve." VA clinicians historically used non-standardized clinical terminologies which are inconsistent within the VA user community as well as within the currently accepted data standards as established by Office of the National Coordinator for Health Information Technology (ONC). Implementation of Native Standardization will allow a streamlined method for data sharing, performing clinical decision support and engaging in national data reporting and analysis. The VA has recently established a process for implementing standard terminology/terminologies within individual clinical domains for the exchange of data. The intent of this effort is to provide the detailed groundwork necessary for industry-wide interoperability. By providing a detailed analysis of the current state of the applicable domains and recommendations regarding the path forward, the Native Domain Standardization supports VA's efforts to remain at the forefront of healthcare data exchange. The local facility Automated Data Processing Application Coordinator (ADPAC) will need to associate the local procedure names in file #71 to Gold Names in file #71.99. It will be necessary to develop a national standard of radiology procedures and map to their respective Current Procedural Terminology (CPT) code and Logical Observation Identifiers Names and Codes (LOINC) will be populated under the direction of the VHA Radiology Program Office prior to implementation of any of the data within these files. The objective of this process is to enable the most user friendly interface as possible in the implementation of the native standardization along with all of the activities required to operationalize the change within the VistA environment and the associated terminology consuming applications. The Radiology ADPAC will match each active entry in the RAD/NUC MED PROCEDURES file (# 71) to an entry in the MASTER RADIOLOGY PROCEDURES file (#71.99) (MRPF). This is all that is required outside the normal day-to-day operations. When a new procedure is entered into the RAD/NUC MED PROCEDURES file (# 71) an email is automatically sent to the NEW TERMINOLOGY RAPID TURNAROUND (NTRT) team for the creation of a new entry in the MRPF. The results of the NTRT process will be one of three possible results. 1) A new entry will be created in the MRPF and will be in the next file release. 2) A match was found in the MRPF and the facility should use that entry for a match. 3) There is no LOINC that matches this procedure and a request for a new LOINC has been submitted. An On Demand report is available to the VHA Radiology Program Office that will allow them to monitor new procedure creation activity. A bulletin will be sent to a local mail group, the VHA Radiology Program Office, and NTRT when a new procedure reaches a specified number of days from creation and it has not been matched to a MASTER RADIOLOGY PROCEDURES file (# 71.99) entry. While the MASTER RADIOLOGY PROCEDURES file (# 71.99) is locked down and cannot be changed at the local facility, the RAD/NUC MED PROCEDURES file (# 71) will remain accessible to the local facility. When creating a new procedure the RA PROCEDURE will use the NEW RAD PROCEDURE WORKUP file (#71.11) as the preliminary work area. When the procedure entry is complete a newly created procedure will be moved to the RAD/NUC MED PROCEDURES file (# 71) and then removed from the NEW RAD PROCEDURE WORKUP file (#71.11). ******************************************** After installing this patch and after the MASTER RADIOLOGY PROCEDURE file (#71.99) is deployed to your facility there is an associated follow on informational patch (RA*5.0*134) that should be installed. The informational patch RA*5.0*134 provides instructions for turning on the sending of NTRT messages to the NTRT group. Related Patches --------------- XU*8*666, HDI*1.0*16, RA*5.0*127, RA*5.0*134 Until all of the patches listed in the Related Patches section are installed and the MASTER RADIOLOGY PROCEDURES file (#71.99) (MRPF) content has been deployed to your facility the ADPAC will not have the ability to interact with the MRPF. The MASTER RADIOLOGY PROCEDURES file (#71.99), distributed with the patch is not populated. Therefore, the options associated to this patch should not be used at this time. In the future, the NTRT team will populate and deploy the MRPF file for all facilities. Prior to the MRPF file population being deployed the ADPAC should ignore all NTRT mailman messages that are generated until the sending of NTRT messages functionality is turned on. When the content of the MASTER RADIOLOGY PROCEDURES file (#71.99) has been deployed the NTRT group sends a message to the NTRT_NOTIFICATION-L listserv. The ADPAC for the facility shall subscribe to this list using the following web site: http://vaww.listserv.domain.ext/scripts/wa.exe. The NTRT group does not own the List Serve application. The List Serve is a VA service. The ADPAC will need to create an account using a username and password that does NOT synchronize with the ADPAC's VA network account. ******************************************** Patch Components: Bulletins Fields Files Input Templates Mailman Group Options Routines Bulletins --------- UNMATCHED RADIOLOGY PROCEDURE New Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- RAD/NUC MED PROCEDURES (# 71) Modified MRPF NAME (# 900) New Exception Flag (# 901) New CREATION DATE (# 902) New LOINC CODE (#903) New MASTER RADIOLOGY SITE (# 71.98) New FACILITY NUMBER (.01) New FACILITY RADIOLOGY ADPAC(#1) New DAYS FOR DEACTIVATION (#2) New MATCHING COMPLETE (#3) New LAST PROCEDURE MAPPED (#4) New DAYS AFTER CREATION BULLETIN (#5) New RADIOLOGY NTRT MAILGROUP (#6) New NTRT ISAAC SCHEMA PATH (#7) New ISAAC ON LINE (#8) New SEEDING COMPLETE (#9) New NTRT AITC PORT (#10) New NTRT IP ADDRESS (#11) New NTRT IP ADDRESS1(#11.5) New NTRT ISAAC SCHEMA NAME (#11.6) New MASTER RADIOLOGY PROCEDURE (# 71.99) New GOLD NAME (#.01) New VUID (#.02) New CPT CODE (# 1) New MRPF LONG NAME (#3;.01) New LOINC (# 2) New LOINC LONG DESCRIPTION (# 2.1) New LOINC SHORT DESCRIPTION (# 2.2) New NEW RAD PROCEDURE WORKUP (#71.11) NAME (#.01) New SUPPRESS RADIOPHARM PROMPT (#2) New REQUIRED FLASH CARD PRINTER New (#3) REQUIRED FLASH CARD FORMAT New (#4) PROMPT FOR MEDS (#5) New TYPE OF PROCEDURE (#6) New STAFF REVIEW REQUIRED (#7) New CPT CODE (#9) New RAD/NM PHYS APPROVAL New REQUIRED(#11) TYPE OF IMAGING (#12) New HEALTH SUMMARY WITH REQUEST New (#13) SINGLE REPORT (#18) New PROMPT FOR RADIOPHARM RX New (#19) CONTRAST MEDIA USED (#20) New DEFAULT RADIOPHARMACEUTICALS New (#50) DEFAULT MEDICATIONS (#55) New FILMS NEEDED (#75) New INACTIVATION DATE (#100) New CONTRAST MEDIA (#125) New DEFAULT CPT MODIFIERS(PROC) New (#135) SYNONYM (#150) New AMIS CODES (#175) New MESSAGE (#200) New DESCENDENTS (#300) New EDUCATIONAL DESCRIPTION New (#500) MODALITY (#731) New MRPF NAME (#900) New Exception Flag (#901) New ENTRY CREATION DATE (#902) New LOINC (#903) New Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- RADNTRT New Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- RA MAP TO MRPF INPUT New RA NEW PROCEDURE TIME BULLETIN OUTPUT New RA SUPERVISOR MENU Modified RADIOLOGY INACTIVATE SERVER New RADIOLOGY ON DEMAND SERVER New RADNEWPRO SERVER New RALOINC ENTER INPUT New RA MAP ONE INPUT New RA MRPF PIN OUTPUT New RA SEEDING DONE INPUT New RA PROCEDURE INPUT Modified 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 ------------- ---- ------------------ -------------------- RA PRO TO MRPF EDIT RAD/NUC MED PROCEDURES (# 71) New RA PROCEDURE EDIT EDIT RAD/NUC MED PROCEDURES (# 71) Modified NEW RAD PROCEDURE EDIT NEW RAD PROCEDURE WORKUP (#71.11) New Additional Information: None New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- None Defect Tracking System Ticket(s) & Overview: -------------------------------------------- N/A Test Sites: ---------- VAMC White City, OR VAMC St. Louis VAMC Chicago (Westside) 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 ------------------------------------------------------------------------ Radiology Technical Manual Binary Automated Data Processing Application Coordinator (ADPAC) Addendum Binary Binary Patch Installation: Pre/Post Installation Overview: There are no pre-installation actions. For post-installation the MASTER RADIOLOGY SITE file (# 71.98) will be set with the facility number and a default of 30 days for the DAYS AFTER CREATION BULLETIN field. The RA NEW PROCEDURE TIME BULLETIN option will be queued to run daily at 3:00 a.m. 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_127

Patch Subject: CORRECT AP AND AS INDEXES FOR PATIENT MERGE Description: ============ This patch addresses the following issues: 1. The RAD/NUC MED ORDERS file (#75.1) AS and AP cross references do not merge during a patient merge. Associated Ticket(s): ===================== 1. I9328296FY16 - PT merge_"AS" cross reference left over during merge process/Pt merge and RAD order problem Associated NSR(s): ================== N/A Participating Test Sites: ========================= UpState New York Boston HCS Ticket Overview: ================ 1. I9328296FY16 - PT merge_"AS" cross reference left over during merge process/Pt merge and RAD order problem Patient Safety Issues: ---------------------- PSPO 3176 Problem: -------- The RAD/NUC MED ORDERS file (#75.1) AS and AP cross references do not merge during a patient merge. These cross references have a non-standard PATIENT file (#2) pointer. The merging of Non-standard PATIENT file (#2) pointers during a patient merge should have been handled by the file developers but were not. Resolution: ----------- The RAD/NUC MED ORDERS file (#75.1) Data Dictionary was modified to delete the old Traditional style "AP" and "AS" xrefs and create New style "AP" and "AS" indexes. The "AP" index will be updated any time the NAME (#.01), PROCEDURE (#2) or DATE DESIRED (#21) fields are modified in the RAD/NUC MED ORDERS (#75.1) file. The "AS" index will be updated any time the NAME (#.01) or REQUEST STATUS (#5) fields are modified in the RAD/NUC MED ORDERS (#75.1) file. Post install routine RA5130P will deleted the old cross references. Files & Fields Associated: File Name (Number) Field Name (Number) New/Mod/Del ---------------------------- ------------------------ ----------- RAD/NUC MED ORDERS (#75.1) NAME (#.01) Modify RAD/NUC MED ORDERS (#75.1) PROCEDURE (#2) Modify RAD/NUC MED ORDERS (#75.1) DATE DESIRED (#21) Modify RAD/NUC MED ORDERS (#75.1) REQUEST STATUS (#5) Modify 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_130

Patch Subject: RTLS SUPPORT FOR CATHETERIZATION LAB Description: ============ The purpose of this patch is to provide an integration between the WaveMark Real Time Location System (RTLS) and VA legacy VistA packages to support important Cardiac Catheterization Lab processes involving automated supply inventory, patients, and staff identification. This patch implements interfaces for queries to the following VistA packages and files: o Generic Inventory Package (GIP), a module of IFCAP used in VistA o New Person file (#200) o Patient file (#2) This patch also populates the new option RTLS Interface Menu [VIAA01 RTLS RPC MENU] with multiple Remote Procedure Calls (RPC). The new menu will be used by the application proxy that was created by Patch VIAA*1.0*1. New Functionality Exported by This Patch: ----------------------------------------- During installation of the patch, the following RPC menu will be populated in VistA: RTLS Interface Menu [VIAA01 RTLS RPC MENU] This is the RTLS interface menu which includes Remote Procedure Calls for multiple packages and files in VistA. Patch Components: ---------------- Files Fields Associated: File Name (Number) Field Number New/Modified/Deleted -------------------------- ------------ -------------------- None Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- None Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- None Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- None Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- None Remote Procedure Calls Associated: Remote Procedure Calls (RPC) Name New/Modified/Deleted --------------------------------- -------------------- VIAA GET EMPLOYEE DATA New VIAA GET INVENTORY POINT ITEMS New VIAA GET ITEM MASTER UPDATE New VIAA GET PATIENT DATA New VIAA SET PAR LEVELS IN GIP New VIAA SET QUANTITY ON HAND New VIAA GET CATHLAB PATCH STATUS New Security Keys Associated: Security Key Name ----------------- None Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- None New Service Requests (NSRs): ---------------------------- None Patient Safety Issues (PSIs): ----------------------------- None Defect Tracking System Ticket(s) & Overview: -------------------------------------------- None Test Sites: ----------- Denver Oklahoma City Salt Lake City Houston Jackon 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. Patch Installation: Pre/Post Installation Overview: ------------------------------- During the post-installation phase the application proxy user secondary menu option will be updated to include all the Remote Procedure Calls (RPC) exported with this patch. No other menu, either primary or secondary, may be assigned to this user. After installation of this patch, every site will need to add the application proxy user to the GIP inventory point that handles the Cath Lab supplies. This is a one-time set up and is not required if the patch is re-installed. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Real+Time+Location+System/Patches/VIAA_1.0_4

Patch Subject: TIU NATIVE DOMAIN STANDARDIZATION Description: ============ **************************** ATTENTION ********************************* MFS Parameters for TIU consists of two patches: Kernel patch XU*8.0*675 and application patch TIU*1.0*309. Application patch TIU*1.0*309 should be installed immediately after installing XU*8.0*675. ************************************************************************ NOTE: Sites should refer to the Deployment, Installation, Back-Out, and Rollback Guide (tiu_1_0_309_ig.pdf) for complete installation instructions. This patch adds a new CODING SYSTEM (#2) multiple to the TIU VHA ENTERPRISE STANDARD TITLE (#8926.1) file for the purpose of interoperability. The TIU VHA ENTERPRISE STANDARD TITLE (#8926.1) file shall be updated to include a new field to store LOINC code field from the respective Standards Development Organizations. This patch addresses the <UNDEFINED>BULL+9^TIUDD61 error reported in Remedy Ticket #241480. The error occurs when a New Term Rapid Turnaround (NTRT) deployment which doesn't modify the STATUS (#.02) field in the EFFECTIVE DATE/TIME (#99.991) multiple of any VHA ENTERPRISE STANDARD TITLE (# 8926.1) file entries in the target VistA system. Examples of NTRT deployments that cause this error are deployments sent to the same VistA domain more than once, and deployments that change properties without activating or inactivating any titles. Associated Remedy Tickets: ========================== INC000000241480 - Error <UNDEFINED>BULL+9^TIUDD61. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Mod/Deleted ---------------------------- ------------------- --------------- TIU VHA ENTERPRISE STANDARD CODING SYSTEM (#2) New TITLE (#8926.1) TIU VHA ENTERPRISE STANDARD TITLE (#8926.1) CODING SYSTEM (#8926.12) CODING SYSTEM (#.01) New CODING SYSTEM (#8926.12) CODE (#.02) New TIU VHA ENTERPRISE STANDARD TITLE (#8926.1) CODING SYSTEM (#8926.12) CODE (#8926.121) CODE (#.01) 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): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- INC000000241480 - <UNDEFINED>BULL+9^TIUDD61 error Problem: -------- An undefined error <UNDEFINED>BULL+9^TIUDD61 occurs during an NTRT deployment which doesn't modify the STATUS (#.02) field in the EFFECTIVE DATE/TIME (#99.991)) multiple of the VHA ENTERPRISE STANDARD TITLES (#8926.1) file in the target VistA system. Examples of NTRT deployments that would cause this error are deployments sent to the same VistA domain more than once, and deployments that change properties without activating or inactivating any titles. Resolution: ----------- Routine TIUDD61 was modified to prevent the error from occurring, by gracefully handling deployments sent to the same VistA domain more than once, and deployments that change properties without activating or inactivating any titles. Test Sites: ---------- NY HARBOR HCS PALO ALTO HCS 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 Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ Title File Name FTP Mode ---------------------------------------------------------------------- TIU Technical Manual tiutm.pdf Binary tiutm.doc Binary Deployment, Installation, tiu_1_0_309_ig.pdf Binary Back-Out, and Rollback Guide tiu_1_0_309_ig.doc Binary Patch Installation: Pre/Post Installation Overview: ------------------------------- It is recommended that a Local Patch Backup is created that can be re-installed in the event patch TIU*1.0*309 must be backed out. Refer to the Deployment, Installation, Back-Out, and Rollback Guide Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Text+Integration+Utility/Patches/TIU_1.0_309

Patch Subject: PCE IMMUNIZATION ENHANCEMENTS Description: ============ The Veterans Health Information Systems and Technology Architecture (VistA) Immunizations Enhancements (VIMM) 2.0 project, Increment 2, builds upon the file structures and standardized data introduced by Increment 1 by adding functional enhancements to the existing VistA Patient Care Encounter (PCE) package. This patch provides the following new features: 1) A new Clinical Reminders index will be created on the V IMMUNIZATION file (#9000010.11). This additional index uses the immunization's CVX code. The indexes are stored in the Clinical Reminders index global as: ^PXRMINDX(9000010.11,"CVX","IP",CVX CODE,DFN,DATE,DAS) ^PXRMINDX(9000010.11,"CVX","PI",DFN,CVX CODE,DATE,DAS) Also, the Clinical Reminders indexes on the V IMMUNIZATION file will be changed to use the EVENT DATE AND TIME field (#1201) (if populated) as the DATE instead of the Visit Date and Time. The Visit Date and Time will be used as DATE only if the EVENT DATE AND TIME field is not populated. 2) The following Application Programming Interfaces (APIs) have been added or modified: a) DATA2PCE^PXAPI (Modified) - Support for the following immunization fields have been added to the INPUTROOT array parameter: VIS Offered/Given To Patient, Remarks, and Ordering Provider b) ENCEVENT^PXKENC and GETENC^PXAPI (Modified) - The following V IMMUNIZATION fields have been added to the returned ^TMP global array: VIS Offered/Given To Patient, Remarks, and Other Diagnosis c) VIS^PXAPI (New) - Returns a Vaccine Information Statement entry d) IMMUN^PXRHS03 (Modified) - Two new optional parameters were added to control: 1) how the return global is sorted, and 2) to allow filtering based off Vaccine Group Name, IEN, or CVX. Also, additional data is returned in the return global. 3) The PX SAVE DATA remote procedure call (RPC) has been modified to provide support for CVX Code, Event Info Source IEN, Route IEN and HL7 Code, Admin Site IEN and HL7 code, Lot # IEN, Event Date/Time, Ordering Provider, VIS, and Remarks. 4) The security codes on the IMMUNIZATION file (#9999999.14) and SKIN TEST file (#9999999.28) will be updated as follows: AUDIT="@", DD="@", DEL="@", LAYGO="@", RD="", and WR="@". 5) The PCE skin test documentation process is updated to include the following: a) Test placement, reading and interpretation b) Code set mapping c) Diagnosis information entry and updates are restricted to users with supervisor access. 6) The PCE immunization documentation process is updated to include the following: a) Lot number, ordering provider, dosage, route of administration, site of administration b) Post-administration reading and interpretation for immunizations that require reading, such as smallpox. c) Diagnosis information entry and updates are restricted to users with supervisor access. 7) Immunization inventory management functionality is added by this patch. This functionality includes allowing authorized users to enter and update information in the IMMUNIZATION LOT file (#9999999.41). This functionality provides for displaying available immunization inventory. Cross reference functionality decrements the number of doses unused when an immunization lot is assigned to a patient's immunization record. 8) Values for the following fields in the V SKIN TEST file (#9000010.12) are moved from existing fields to new fields by a post-install process. The old fields and their data are removed from the file after moving the data. From Field To Field -------------- ------------- DIAGNOSIS (#.08) --> PRIMARY DIAGNOSIS (#801) DIAGNOSIS 2 (#.09) --> DIAGNOSIS 2 (#802) DIAGNOSIS 3 (#.1) --> DIAGNOSIS 3 (#803) DIAGNOSIS 4 (#.11) --> DIAGNOSIS 4 (#804) DIAGNOSIS 5 (#.12) --> DIAGNOSIS 5 (#805) DIAGNOSIS 6 (#.13) --> DIAGNOSIS 6 (#806) DIAGNOSIS 7 (#.14) --> DIAGNOSIS 7 (#807) DIAGNOSIS 8 (#.15) --> DIAGNOSIS 8 (#808) 9) When documenting an historical immunization, the user will now be able to select inactive immunizations that are marked as Selectable For Historic. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- V IMMUNIZATION (#9000010.11) IMMUNIZATION (#.01) Modified PATIENT NAME (#.02) Modified VISIT (#.03) Modified SERIES (#.04) Modified LOT (#.05) ) Modified REACTION (#.06) Modified CONTRAINDICATED (#.07) Modified DOSE OVERRIDE (#.08) Modified INJECTION SITE (#.09) Modified VOLUME (#.11) Modified DATE OF VAC INFO STATEMENT (#.12) Modified CREATED BY V CPT ENTRY (#.13) Modified VAC ELIGIBILITY (#.14) Modified IMPORT FROM OUTSIDE REGISTRY Modified (#.15) NDC (#.16) Modified ADMINISTRATIVE NOTES (#1) Modified VIS OFFERED/GIVEN TO PATIENT (multiple field #2, sub-file #9000010.112) Modified VIS OFFERED/GIVEN TO PATIENT (#.01) of the VIS OFFERED/GIVEN TO PATIENT sub-file (#9000010.112) Modified DATE VIS OFFERED/GIVEN (#.02) of the VIS OFFERED/GIVEN TO PATIENT sub-file (#9000010.112) Modified EVENT DATE AND TIME (#1201) Modified ORDERING PROVIDER (#1202) Modified CLINIC (#1203) Modified ENCOUNTER PROVIDER (#1204) Modified DATE/TIME RECORDED (#1205) Modified IMMUNIZATION DOCUMENTER (#1206) Modified LOT NUMBER (#1207) Modified PARENT (#1208) Modified EXTERNAL KEY (#1209) Modified OUTSIDE PROVIDER NAME (#1210) Modified ANCILLARY POV (#1213) Modified USER LAST UPDATE (#1214) Modified ORDERING LOCATION (#1215) Modified DATE/TIME ENTERED (#1216) Modified ENTERED BY (#1217) Modified DATE/TIME LAST MODIFIED (#1218) Modified LAST MODIFIED BY (#1219) Modified EVENT INFORMATION SOURCE (#1301) Modified ROUTE OF ADMINISTRATION (#1302) Modified SITE OF ADMINISTRATION (BODY) (#1303) Modified PRIMARY DIAGNOSIS (#1304) Modified DOSE (#1312) Modified DOSAGE (#1312.5) New DOSE UNITS (#1313) 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 EDITED FLAG (#80101) Modified AUDIT TRAIL (#80102) Modified COMMENTS (#81101) Modified VERIFIED (#81201) Modified PACKAGE (#81202) Modified DATA SOURCE (#81203) Modified V SKIN TEST (#9000010.12) SKIN TEST (#.01) Modified PATIENT NAME (#.02) Modified VISIT (#.03) Modified RESULTS (#.04) Modified READING (#.05) Modified DATE READ (#.06) Modified READER (#.07) New DIAGNOSIS (#.08) Deleted DIAGNOSIS 2 (#.09) Deleted DIAGNOSIS 3 (#.1) Deleted DIAGNOSIS 4 (#.11) Deleted DIAGNOSIS 5 (#.12) Deleted DIAGNOSIS 6 (#.13) Deleted DIAGNOSIS 7 (#.14) Deleted DIAGNOSIS 8 (#.15) Deleted CODING SYSTEM (multiple field #3, sub-file #9000010.123) New CODING SYSTEM (#.01) of the CODING SYSTEM sub-file (#9000010.123) New CODE (multiple field #.02, sub-file #9000010.1231 of the CODING SYSTEM sub-file (#9000010.123) New CODE (#.01) of the CODE sub-file (#9000010.1231) New EVENT DATE AND TIME (#1201) Modified ORDERING PROVIDER (#1202) Modified ENCOUNTER PROVIDER (#1204) Modified SKIN TEST PLACEMENT RECORDED (#1211) New ANATOMIC LOCATION OF PLACEMENT (#1212) New HOURS READ POST-PLACEMENT (#1214) New SKIN TEST READING RECORDED (#1220) New READING COMMENTS (#1301) New PRIMARY DIAGNOSIS (#801) New DIAGNOSIS 2 (#802) New DIAGNOSIS 3 (#803) New DIAGNOSIS 4 (#804) New DIAGNOSIS 5 (#805) New DIAGNOSIS 6 (#806) New DIAGNOSIS 7 (#807) New DIAGNOSIS 8 (#808) New EDITED FLAG (#80101) Modified AUDIT TRAIL (#80102) Modified PLACEMENT COMMENTS (#81101) Modified VERIFIED (#81201) Modified PACKAGE (#81202) Modified DATA SOURCE (#81203) Modified IMMUNIZATION LOT (#9999999.41) LOT NUMBER (#.01) Modified MANUFACTURER (#.02) Modified STATUS (#.03) Modified VACCINE (#.04) Modified VACCINE #2 (#.05) Modified VACCINE #3 (#.06) Modified VACCINE #4 (#.07) Modified VACCINE #5 (#.08) Modified EXPIRATION DATE (#.09) Modified STARTING COUNT (#.11) Modified DOSES UNUSED (#.12) Modified VACCINE SOURCE (#.13) Modified HEALTH CARE FACILITY (#.14) Modified LOW SUPPLY ALERT (#.15) Modified LOT NUMBER FOR EXPORT (#.16) Modified NDC CODE (#.17) Modified NDC CODE (VA) (#.18) 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 ----------- ---- -------------------- PXTT EDIT IMMUNIZATION LOT Run Routine Modified PXVTASK-NIGHT Run Routine Modified Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A RPCs Associated: RPC New/Modified/Deleted ------------- -------------------- PX SAVE DATA Modified Security Keys Associated: Security Key Name New/Modified/Deleted ----------------- -------------------- PXV IMM INVENTORY MGR New 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 Blood Bank Clearance: --------------------- N/A Remedy Ticket(s) & Overview: ---------------------------- N/A Test Sites: ---------- Cleveland, OH Hampton, VA 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_R20160121.PDF (binary) V. 1.0 User Manual Patient Care Encounter (PCE) PX_1_TM_R20160129.PDF (binary) V.1.0 Technical Manual Clinical Reminders (PXRM) PXRM_INDEX_TM.PDF (binary) Index Technical Manual VIMM Patch PX*1*210 PX_1_P210_IG.PDF (binary) Installation Guide Patch Installation: Pre/Post Installation Overview: ------------------------------- The pre-installation process removes seven MUMPS cross-references that existed only in early versions of this patch. The post-installation process does the following: a) Tasks a job to rebuild the Clinical Reminder's V Immunization index. When installing the patch, the user will be prompted when this task 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_210

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: GREATER THAN 90 DAYS SUPPLY ENHANCEMENT & MORE Description: ============ This patch is part of the Pharmacy Safety Updates project which was established to address specific New Service Requests (NSRs) as well as Remedy Ticket(s) and a Patient Safety Issue (PSI) related to the VistA Pharmacy applications as approved by the Health Systems Enterprise Systems Manager(ESM). This project is comprised of patches from five different applications, as shown below: APPLICATION/VERSION PATCH ----------------------------------------------------------------- PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*189 OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*444 INPATIENT MEDICATIONS (IM) V.5.0 PSJ*5*313 NATIONAL DRUG FILE (NDF) V. 4.0 PSN*4*429 INTEGRATED BILLING (IB) V. 2.0 IB*2*545 The following New service Requests (NSRs) are being addressed by this patch: NSRs 20060601/20111206 Allow Dispensing of Greater Than 90 Day Supply --------------------------------------------------------------------------- The Outpatient Pharmacy and supporting VistA applications are being modified to allow dispensing of more than 90 day supply fill for outpatient prescriptions. The new limit will be 365 days and will be set for each drug individually. See below for more information on specific menu options related to this enhancement. NSR 20110308 Addition of a STRENGTH Property to IV ADDITIVES and Premixed IV SOLUTIONS ---------------------------------------------------------------------------- Although patches PSJ*5*289 and PSS*1*174 introduced quite a few enhancements to the IV Additives and IV Solutions ordering functionality they did not go far enough in addressing all the issues originally in the NSR. Patches PSJ*5*313 and PSS*1*189 will extend the display of the IV Additive strength to other parts of the Inpatient Medications and Pharmacy Data Management applications. In addition, it will also impose a new rule where an Orderable Item can only have one IV Solution for a specific volume when it is marked to be used in the CPRS IV Fluid Order Entry. NSR 20080907 Inactivate Pharmacy Standard Schedule ---------------------------------------------------------------------------- This enhancement is a conversion of an existing Class III software solution that permits an entry in the ADMINISTRATION SCHEDULE file (#51.1) to be marked as INACTIVE via the Standard Schedule Edit [PSS SCHEDULE EDIT] option. Once marked INACTIVE the schedule is no longer shown on the CPRS ADMINISTRATION SCHEDULE list. The following Pharmacy Data Management functionality was modified: 1. New MAXIMUM DAYS SUPPLY field (#66) in the DRUG file (#50) This new field shown below was added to the DRUG file (#50) for storing the local maximum day supply value for a medication in an outpatient prescription. Field Name: MAXIMUM DAYS SUPPLY Format: Numeric INPUT TRANSFORM: D MXDAYSUP^PSSDDUT2 HELP-PROMPT: This is the maximum number of days supply for this drug. Enter ?? for important information regarding default values and copays. DESCRIPTION: This field is used to determine the maximum number for days supply that may be assigned to this drug. If this field is left blank, the MAXIMUM DAYS SUPPLY is set to a default of 90 unless the drug is a controlled substance or Clozapine. Any value greater than 90 increases the number of potential copay units above 3. The maximum value allowed for this field is 365 (days) for most drugs, however: - Schedule 2 controlled substances have a 30-day maximum days supply limit - Schedules 3 thru 5 controlled substances have a 90-day maximum days supply limit - The maximum number of days supply for this drug cannot exceed the National Drug File (NDF) maximum value if it exists - No value can be entered for Clozapine drugs as the maximum days supply is controlled by the Clozapine functionality 2. ADMINISTRATION SCHEDULE file (#51.1) a) A new field named INACTIVE (#12) shown below was added to the ADMINISTRATION SCHEDULE file (#51.1) to allow the filtering inactive schedules when providing a list to the CPRS application. Field Name: INACTIVE Format: Set of Codes ('1' FOR YES) HELP-PROMPT: Answer YES to mark this administration schedule entry as inactive. DESCRIPTION: This field is used to indicate that a Standard Schedule is inactive. Inactive schedules are filtered from the list of schedules sent to CPRS for selection when users are placing a medication order. b) The upper limit for the FREQUENCY (IN MINUTES) field (#2) was increased from 129,600 (90 days) to 525,600 (365 days). 3. MEDICATION INSTRUCTION file (#51) The upper limit for the FREQUENCY (IN MINUTES) field (#31) was increased from 129,600 (90 days) to 525,600 (365 days). 4. IV SOLUTIONS file (#52.7) New INPUT TRANSFORMS have been added to the VOLUME (#2) and USED IN IV FLUID ORDER ENTRY (#17) to enforce the following new rule introduced relating to this file: Rule: An Orderable Item can have only ONE IV solution with a specific volume when it is marked to be used in the IV Order Dialog. 5. PSSCOMMON input template The PSSCOMMON input template used by the Drug File Enter/Edit [PSS DRUG ENTER/EDIT] option was modified to include the new MAXIMUM DAYS SUPPLY field (#66) in the DRUG file (#50) so that it can be edited along with the other fields in this option. 6. PSSJ SCHEDULE EDIT Input template The PSSJ SCHEDULE EDIT input template used by the Standard Schedule Edit [PSS SCHEDULE EDIT] option was modified to include the new INACTIVE field (#12) in the ADMINISTRATION SCHEDULE file (#51.1) so that it can be edited along with the other fields in this option. 7. Edit Orderable Items [PSS EDIT ORDERABLE ITEMS] option This option was modified to display the IV Additive Strength value as seen below: ... Orderable Item -> PIPERACILLIN/TAZOBACTAM Dosage Form -> INJ Dispense Drugs: --------------- PIPERACILLIN 3/TAZOBACTAM 0.375GM/VI INJ PIPERACILLIN 2/TAZOBACTAM 0.25GM/VI INJ PIPERACILLIN 4/TAZOBACTAM 0.5GM/VI INJ PIPERACILLIN/TAZOBACTAM (A) Additive Strength: 3.375 GM PIPERACILLIN/TAZOBACTAM (A) Additive Strength: 2.25 GM PIPERACILLIN/TAZOBACTAM (A) Additive Strength: 4.5 GM ... 8. Primary Solution File (IV) [PSSJI SOLN] option This option was modified to enforce a new rule introduced to ensure that an Orderable Item can only have 1 active IV SOLUTION linked to it with a specific VOLUME when the IV SOLUTION is marked YES for the USED IN IV FLUID ORDER ENTRY field (#17). When they user tries to perform an edit that breaks this rule by editing the screen fields VOLUME, USED IN IV FLUID ORDER ENTRY or INACTIVATION DATE, the error message below will be displayed and the editing won't be permitted. Only one Active IV Solution with a specific volume can be linked to an Orderable Item or Dispense Drug when the IV Solution is marked to be used in the CPRS IV Fluid Order Entry. 9. Drug Enter/Edit [PSS DRUG ENTER/EDIT] option a) This option was modified to allow entry of the new MAXIMUM DAY SUPPLY ... NCPDP DISPENSE UNIT: EACH// NCPDP QUANTITY MULTIPLIER: 1// MAXIMUM DAYS SUPPLY: ?? This field is used to determine the maximum number for days supply that may be assigned to this drug. The maximum value allowed for this field is 365 (days) for most drugs, however: - Schedule 2 controlled substances have a 30-day maximum days supply limit - Schedules 3 thru 5 controlled substances have a 90-day maximum days supply limit - The maximum number of days supply for this drug cannot exceed the National Drug File (NDF) maximum value if it exists - No value can be entered for Clozapine drugs as the maximum days supply is controlled by the Clozapine functionality MAXIMUM DAYS SUPPLY: PRICE PER DISPENSE UNIT: 0.8280 ... b) The exact same change described above in #8 was applied to this option where the user can create, edit and link IV Solution entries to a dispense drug. 10. Lookup into Dispense Drug File [PSS LOOK] option This option was modified to display the new MAXIMUM DAYS SUPPLY (#66) field in the DRUG file (#50) along with the other dispense drug fields for the dispense drug selected, as shown below: ... DISPENSE UNIT: VA DISPENSE UNIT: CAP DISPENSE UNITS/ORDER UNIT: 20 PRICE/DISPENSE UNIT: 0.8280 NCPDP DISPENSE UNIT: EACH NCPDP QUANTITY MULTIPLIER: 1.000 MAXIMUM DAYS SUPPLY: 100 APPL PKG USE: Outpatient Unit Dose Non-VA Med STRENGTH: 10 UNIT: MG POSSIBLE DOSAGES: ... 11. Standard Schedule Edit [PSS SCHEDULE EDIT] option This option was modified to add the new INACTIVE field (#12) in the ADMINISTRATION SCHEDULE file (#51.1) to be updated for a schedule. ... OTHER LANGUAGE EXPANSION: INACTIVE: ?? This field is used to indicate that a Standard Schedule is inactive. Inactive schedules are filtered from the list of schedules sent to CPRS for selection when users are placing a medication order. Choose from: 1 YES INACTIVE: ... 12. Administration Schedule File Report [PSS SCHEDULE REPORT] option This option was modified to display the new INACTIVE field (#12) created in the ADMINISTRATION SCHEDULE file (#51.1) as seen below: ADMINISTRATION SCHEDULE FILE REPORT (All) PAGE: NN ---------------------------------------------------------------------- ... *Q4H STANDARD ADMINISTRATION TIMES: 01-05-09-13-17-21 OUTPATIENT EXPANSION: EVERY 4 HOURS OTHER LANGUAGE EXPANSION: SCHEDULE TYPE: CONTINUOUS FREQUENCY (IN MINUTES): 240 EXCLUDE FROM ALL DOSE CHECKS: EXCLUDE FROM DAILY DOSE CHECK: INACTIVE: YES ... 13. Dispense Drug/Orderable Item Maintenance [PSS MAINTAIN ORDERABLE ITEMS] & Drug Enter/Edit [PSS DRUG ENTER/EDIT] options A new rule described below is being introduced which is related to the relationship between IV Solutions and Orderable Items. Rule: An Orderable Item can only have ONE IV solution with a specific volume when it is marked to be used in the CPRS IV Order Dialog. This option was modified to check every time the user tries to link a dispense drug to an orderable item whether the new rule is being broken or not. If the new rule is being broken the message below will be displayed and the user will not be able to proceed with linking the drug to the orderable item. Matching [Dispense Drug Name] to [Orderable Item Name] would cause the orderable item to have more than one Active IV Solution with the same volume marked to be used in the IV FLUID ORDER ENTRY, which is not allowed. Please, review the IV Solutions associated with this drug before matching it to this orderable item or match it to a different orderable item. 14. IV Solution Pre-Install Manual Clean-up (Environment Check routine) An environment check routine will run before the patch is installed to ensure that an orderable item does not have more than one IV Solution with the same volume when they are marked YES to be used in the CPRS IV Fluid Order Entry. If at least one orderable item entry is found, the patch installation will be aborted and a Mailman message will be sent to all users holding the following security keys: PSIVMGR, PSJI MGR, PSNMGR. The message will contain a list of all orderable items that need to be cleaned up, as seen in the sample message below: Subj: Duplicate IV Solution Volume under same Orderable Item [#215733] From: PATCH PSS*1*189 In 'IN' basket. Page 1 ------------------------------------------------------------------------- The list below shows IV Solutions in your database that need to be cleaned up before patch PSS*1*189 can be installed. Rule: An Orderable Item can only have ONE IV solution with a specific volume when it is marked to be used in the IV Order Dialog. Run Date/Time: Jun 12, 2015@09:49:16 ------------------------------------------------------------------------- ORDERABLE ITEM (IEN) IV DISPENSE DRUG (IEN) IV SOLUTION (IEN) ------------------------------------------------------------------------- DEXTROSE (196) Solution Volume: 1000 ML DEXTROSE 10% IN WATER (620) DEXTROSE 10% (7) DEXTROSE 5% IN 0.45% NS (623) DEXTROSE 5% 1/2 NS (10) DEXTROSE 5% 1000ML INJ (627) 5% DEXTROSE (1) 15. IV Solution Post-Install Automatic Clean-up (Post-install routine) IV Solutions that are no longer used, meaning that either the IV Solution and/or the Dispense Drug and/or the Orderable Item are marked INACTIVE will have the field USED IN IV FLUID ORDER ENTRY set to 'NO'. A list of such IV Solutions will be sent to all users holding the following security keys: PSIVMGR, PSJI MGR, PSNMGR. The message will contain a list of all IV Solutions that have been automatically updated as seen in the sample message below: Subj: Auto-update of the IV Solution file [#216328] 08/18/15@09:58 From: PATCH PSS*1*189 In 'IN' basket. Page 1 *New* ------------------------------------------------------------------------- The list below shows IV Solutions in your database that had the field USED IN IV FLUID ORDER ENTRY set to 'NO' because either the Orderable Item, the Dispense Drug or the IV Solution itself was marked INACTIVE. Run Date/Time: Aug 18, 2015@09:58:38 ------------------------------------------------------------------------- ORDERABLE ITEM (IEN) IV DISPENSE DRUG (IEN) IV SOLUTION (IEN/VOLUME) ------------------------------------------------------------------------- CEFAZOLIN (106) CEFAZOLIN SOD 1GM INJ (1498) 20% DEXTROSE (2/500 ML) *** INACTIVE DATE: JAN 11, 1994 *** 20% DEXTROSE (11/500 ML) *** INACTIVE DATE: JAN 11, 1994 *** 16. New API for CPRS: $$MAXDS^PSSUTIL1 This new API was created for CPRS to retrieve the Maximum Days Supply value for a specific medication. This API is available to CPRS through the Integration Control Registration (ICR) #3239. Below is a detailed description of the API. $$MAXDS^PSSUTIL1(INPUT) This API accepts an array containing the Pharmacy Orderable Item (required) and Dispense Drug (optional) and returns the maximum number of Days Supply allowed to be dispensed for the specific medication. Parameters: Input: INPUT("PSOI") (Required) Pointer to the PHARMACY ORDERABLE ITEM file (#50.7). INPUT("DRUG") (Optional) Pointer to the DRUG file (#50). This parameter is optional. If not passed, the API will return the highest value from all the dispense drugs linked to the Pharmacy Orderable Item. Output $$MAXDS Maximum number of days supply that can be dispensed for the orderable item and/or dispense drug. 17. IV Additives and Solutions - Display "INACTIVATION DATE" The INACTIVATION DATE will display whenever a VistA lookup is done on IV Additives and Solutions. This was accomplished by making the following two fields identifiers: FIELD NAME FIELD NUMBER FILE NAME/NUMBER ---------------------------------------------------------- INACTIVATION DATE 12 IV ADDITIVES (#52.6) INACTIVATION DATE 8 IV SOLUTIONS (#52.7) Note: The following 'HELP'-PROMPT text will display for fields 8 &12 "Enter the date this drug was inactivated." ********************* EXAMPLE(1) ADDITIVES ********************* Inpatient Drug Management - Additives File [PSSJI DRUG] Select Inpatient Drug Management Option: Additives File Select IV ADDITIVES PRINT NAME: PIPERACILLIN Lookup: IV ADDITIVES PRINT NAME 1 PIPERACILLIN/TAZOBACTAM Additive Strength: 3.375 GM 2 PIPERACILLIN/TAZOBACTAM Additive Strength: 2.25 GM 3 PIPERACILLIN/TAZOBACTAM 03-5-2015 Additive Strength: 4.5 GM ********************* EXAMPLE(2) SOLUTIONS ********************* Inpatient Drug Management - Primary Solution File (IV) Select Inpatient Drug Management Option: PRImary Solution File(IV) Select IV SOLUTIONS PRINT NAME: DEXTROSE 5% / NACL Lookup: PRINT NAME 1 DEXTROSE 5% / NACL 0.2% 1000 ML 2 DEXTROSE 5% / NACL 0.33% 1000 ML 3 DEXTROSE 5% / NACL 0.45% 1000 ML 12-03-15 4 DEXTROSE 5% / NACL 0.9% 1000 ML ********************* END EXAMPLES ********************* Patch Components ================ Files & Fields Associated: File Name (#) Field Name (#) New/Modified/Deleted ------------------ ----------------------------------- -------------------- DRUG (#50) MAXIMUM DAYS SUPPLY (#66) New MEDICATION INSTRUCTION (#51) FREQUENCY (IN MINUTES) (#31) Modified ADMINISTRATION SCHEDULE (#51.1) FREQUENCY (IN MINUTES) (#2) Modified INACTIVE (#12) New IV ADDITIVES (#52.6) INACTIVATION DATE (#12) Modified IV SOLUTIONS (#52.7) VOLUME (#2) Modified INACTIVATION DATE (#8) Modified USED IN IV FLUID ORDER ENTRY (#17) 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 ------------- ----- ------------------------- -------------------- PSSCOMMON INPUT DRUG (#50) Modified PSSJ SCHEDULE EDIT INPUT ADMINISTRATION SCHEDULE (#51.1) Modified New Service Requests (NSRs): ---------------------------- 20060601 20111206 20110308 20080907 Patient Safety Issues (PSIs): ----------------------------- PSPO00002098 PSPO00001088 Remedy Ticket(s) & Overviews: ----------------------------- N/A TEST Sites: =========== NEW YORK HARBOR HCS LOUISVILLE, KY HEARTLAND EAST Documentation Retrieval Instructions: ------------------------------------- Updated documentation describing the new functionality introduced by this patch is available. The preferred method is to retrieve the files from the ANONYMOUS.SOFTWARE directory on download.vista.domain.ext. using secure file transfer protocol. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server as follows: Albany ftp.domain.ext <ftp://ftp.domain.ext> Hines ftp.domain.ext <ftp://ftp.domain.ext> Salt Lake City ftp.domain.ext <ftp://ftp.domain.ext> The documentation will be in the form of Adobe Acrobat files. Documentation can also be retrieved from the VA Software Documentation Library (VDL) on the Internet at the following address: http://www4.domain.ext/vdl. File Description File Name FTP Mode -------------------------------------------------------------------------- PHARMACY DATA MANAGEMENT RELEASE NOTES PSS_1_P189_RN.PDF BINARY PHARMACY DATA MANAGEMENT INSTALLATION PSS_1_P189_IG.PDF BINARY GUIDE PHARMACY DATA MANAGEMENT USER MANUAL PSS_1_UM_R0616.PDF BINARY Patch Installation: Pre Installation Overview ------------------------- This project is comprised of patches from five different applications as listed here. The patches will get released together and the suggested installation order is as shown. An installation guide released with patch PSS*1*189, discusses the installation process as PSS*1*189 is the patch that must be installed first. APPLICATION/VERSION PATCH ----------------------------------------------------------------- PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*189 OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*444 INPATIENT MEDICATIONS (IM) V.5.0 PSJ*5*313 NATIONAL DRUG FILE (NDF) V. 4.0 PSN*4*429 INTEGRATED BILLING (IB) V. 2.0 IB*2*545 ----------------------------------------------------------------- Item #14 above describes in detail the pre-installation requirement for installing this patch. In summary, the process is required because a new rule will be introduced by this patch that will enforce the following: An Orderable Item can only have ONE IV solution with a specific volume when it is marked to be used in the IV Order Dialog. ***Please note**** The pre-installation environment check routine will only execute in production environments. Post Installation Overview -------------------------- Item #15 above describes in detail the post-installation process for automatically setting the USED IN IV FLUID ORDER ENTRY field (#17) in the IV SOLUTIONS file (#52.7) to 'NO' for inactive entries. This will prevent inactive entries from being made active again and breaking the rule described above. 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_189

Patch Subject: QUICK ORDER UTILITY FOR CLINIC ORDERS Description: ============ This patch contains several enhancements to the OE/RR package. Some of the included items are meant to be used as reference and/or preparation for the forthcoming release of CPRS GUI v30.B (OR*3.0*350). NEW DISPLAY GROUPS AND ORDER DIALOGS OE/RR SUPPLY ORDERABLE ITEM REPORT OUTPATIENT PHARMACY QUICK ORDER SEARCH DELETE QUICK ORDERS via ORCM QUICK ORDERS and ORCM QUICK ORDER BY USER EARLIEST APPROPRIATE DATE VALUES FOR CONSULT QUICK ORDERS CREATING CLINIC QUICK ORDERS FROM INPATIENT QUICK ORDERS ======================================================================== ==============NEW DISPLAY GROUPS AND ORDER DIALOGS====================== ======================================================================== The following new DISPLAY GROUPS and ORDER DIALOGS are being distributed with this patch. DISPLAY GROUPS CLINIC MEDICATIONS CLINIC INFUSIONS SUPPLIES/DEVICES ORDER DIALOGS CLINIC OR PAT FLUID OE PSJ OR CLINIC OE PSO SUPPLY ======================================================================== ===============OE/RR SUPPLY ORDERABLE ITEM REPORT======================= ======================================================================== In preparation for the release of CPRS v30.b, with the updates to the Supply Order dialog, the definition of a supply item is changing. Therefore, a report is included in this patch to allow you to review items on your system that will be identified as supplies and, therefore, will be available to that dialog. This report lists all orderable items that resolve to a pharmacy supply item. It will list all quick order dialogs that reference the supply orderable item, as well as all clinical reminders that reference either the supply orderable item or the supply quick order dialog. If the installation is not queued, the installer will be prompted for the recipients of this report. Otherwise, the person queueing the installation will be the only recipient. ======================================================================== ==============OUTPATIENT PHARMACY QUICK ORDER SEARCH==================== ======================================================================== CPRS v30.b will remove the option of DONE as a priority on Outpatient Medication orders. Some sites are using this priority in Quick Orders. In preparation for the release of 30.b, a report is being provided to allow sites time to develop new Quick Orders. This report lists all outpatient pharmacy quick orders that have a priority of DONE. The report output shows the quick order name, any "disable" text and if the quick order is part of an order set/menu or referenced by any Clinical Reminder Elements or Groups. ======================================================================== =DELETE QUICK ORDERS via ORCM QUICK ORDERS and ORCM QUICK ORDER BY USER= ======================================================================== Patch OR*3*245 removed the ability to delete quick orders (QO) and personal quick orders from the ORDER DIALOG file (#101.41). This was done to prevent dangling pointers in files that point to ORDER DIALOG. Reference Remedy ticket #130403 and/or the OR*3*245 patch description for additional background information. This patch, OR*3*389, restores the ability to delete quick orders. When a quick order is selected for deletion, files that point to ORDER DIALOG are checked for possible pointers. As of this patch release, the files and fields checked for pointers are: ORDER (#100) via the DIALOG (#2) and ITEM ORDERED (#7) fields DISPLAY GROUP (#100.98) via the DEFAULT DIALOG (#4) field REMINDER DIALOG (#801.41) via the FINDING ITEM (#15) and the ADDITIONAL FINDINGS (#.01) field of the ADDITIONAL FINDINGS subfile (#801.4118) If no items are found pointing to the selected QO, then deletion may proceed. If any pointers are found, the user will not be able to delete the quick order but may choose to disable it. Any pointers found will be displayed to the user. The output will be the file number, IEN, and NAME (.01) of the item that is pointing to the quick order selected for deletion. Any items displayed from ORDER (#100) will display "N/A" for NAME as those file entries do not have a NAME field. Reference the following two examples of a successful delete and a disable when pointers are detected. Example 1: No pointers to the selected QO ----------------------------------------- ORCM QUICK ORDERS Enter/edit quick orders Select QUICK ORDER NAME: SAMPLE QO ORDER NO POINTERS NAME: SAMPLE QO ORDER NO POINTERS// @ Are you sure you want to delete this quick order? YES ...deleted. Example 2: Items pointing to selected QO ---------------------------------------- Select QUICK ORDER NAME: SAMPLE QO WITH POINTERS NAME: SAMPLE QO WITH POINTERS Replace @ Cannot delete - other file entries point to this order dialog! SAMPLE QO WITH POINTERS is pointed to by: FILE # IEN NAME ------------------------ 100 14522646 N/A 100 14522647 N/A 100.98 68 ZZTEST DISPLAY GROUP 801.41 1754 ZZTEST DLG ELEMENT Would you like to disable this quick order? YES// Enter disable message: DISABLE: Do not use this QO. Call x12345 (This quick order has been disabled) NAME: SAMPLE QO WITH POINTERS Replace^ To facilitate the location of items pointing to a given quick order, the ORDER (#100) file data dictionary is being modified by this patch. The DIALOG (#2) and ITEM ORDERED (#7) fields are each being modified by adding a new cross reference. DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE ------------------------------------------------------------------------- 100,2 DIALOG 0;5 VARIABLE POINTER (Req'd) FILE ORDER PREFIX LAYGO MESSAGE 19 1 OPT n OPTION 101 2 PRO n PROTOCOL 101.41 3 DLG n DIALOG LAST EDITED: FEB 26, 2014 HELP-PROMPT: Enter the dialog that was used to create this order. DESCRIPTION: This is the dialog that created this order. NEW-----> CROSS-REFERENCE: 100^C 1)= S ^OR(100,"C",$E(X,1,30),DA)="" 2)= K ^OR(100,"C",$E(X,1,30),DA) Allows retrieval of the orders placed for a given ORDER DIALOG. 100,7 ITEM ORDERED 3;4 VARIABLE POINTER FILE ORDER PREFIX LAYGO MESSAGE 19 1 MISC n PROTOCOL 60 2 LAB n LAB TEST 101.41 3 DIALOG n ORDER DIALOG LAST EDITED: FEB 28, 2014 HELP-PROMPT: Enter the item ordered. DESCRIPTION: This is the variable pointer to the file and item ordered. NEW-----> CROSS-REFERENCE: 100^D 1)= S ^OR(100,"D",$E(X,1,30),DA)="" 2)= K ^OR(100,"D",$E(X,1,30),DA) Allows retrieval of the orders placed for a given ORDER DIALOG. These new cross-references are created during the post-install process. A tasked job is created that will immediately begin running in the background to create the new cross-references. An email is sent to the installer indicating whether the background job successfully completed or was stopped and needs to be re-started. The message subject will be: PATCH OR*3.0*389 ORDER RE-INDEX STATUS. ======================================================================== =======EARLIEST APPROPRIATE DATE VALUES FOR CONSULT QUICK ORDERS======== ======================================================================== If the installation is not queued, the installer will be prompted for the recipients of this report. Otherwise, the person queueing the installation will be the only recipient. That person should forward the message to the person(s) responsible for managing consult quick orders at the facility. The report contains Consult and Procedure quick orders with a default value stored in the Earliest Appropriate Date (EAD) field. The output for each order found will consist of three values: Internal entry number of the quick order in from ORDER DIALOG (#101.41) The NAME (.01 field) of the quick order The value found for the Earliest Appropriate Date This list of quick orders should be reviewed in preparation for the installation of OR*3*350 and GMRC*3.0*81. These patches are renaming the EAD field to CLINICALLY INDICATED DATE (CID) and also replacing the ORCDGMRC EARLIEST DATE DEFAULT parameter (which can only be set at the PACKAGE level) with a new parameter, ORCDGMRC CLIN IND DATE DEFAULT, which may be set at the DIVISION, SYSTEM, and PACKAGE levels. The new PACKAGE setting for the ORCDGMRC CLIN IND DATE DEFAULT parameter will be null, which will force a provider to actively choose a value for the EAD field when placing consult orders. Local settings may be chosen for the DIVISION and SYSTEM levels in order to have the CID field pre-populated. The list of consult quick orders can be useful if a local decision is made to change the value of the parameter. When your facility installs OR*3*350, part of that installation will capture any PACKAGE level value found for ORCDGMRC EARLIEST DATE DEFAULT and use that value to set the SYSTEM level for the new CID-related parameter ORCDGMRC CLIN IND DATE DEFAULT. For example, if your facility has ORCDGMRC EARLIEST DATE DEFAULT set to "TODAY" at the PACKAGE level, the OR*3*350 installation will set ORCDGMRC CLIN IND DATE DEFAULT to "TODAY" at the SYSTEM level. If your facility opts to change the value for the CID parameter, that value is not automatically detected by any saved quick orders. Any saved quick orders must be edited in order for them to reflect the new parameter value. Example: Change the CID parameter from TODAY to T+7D Clinically Indicated Date Default may be set for the following: 1 Division DIV [choose from INSTITUTION] 2 System SYS [TEST.DOMAIN.EXT] 3 Package PKG [ORDER ENTRY/RESULTS REPORTING] Enter selection: 2 System TEST.DOMAIN.EXT Setting Clinically Indicated Date Default for System: TEST.DOMAIN.EXT Value: TODAY// T+7D **Now, examine a saved quick order and see that the QO still retains the previously saved value.** Select Order Menu Management <TEST ACCOUNT> Option: QO Enter/edit quick orders Select QUICK ORDER NAME: TEST CID PROMPT NAME: TEST CID PROMPT Replace DISPLAY TEXT: TEST CID PROMPT// VERIFY ORDER: YES// DESCRIPTION: No existing text Edit? NO// ENTRY ACTION: Procedure: ERCP// Service: GASTROENTEROLOGY// Reason for Request: No existing text Edit? No// (No) Category: OUTPATIENT// Urgency: ROUTINE// Clinically indicated date:TODAY// <-- NOTE PREVIOUS VALUE. DELETE THIS VALUE TO HAVE QO REFLECT CURRENT. Clinically indicated date:TODAY// @ Are you sure you want to delete this value? NO// y YES **Re-examine the QO and see that the CID value is now current.** Select Order Menu Management <TEST ACCOUNT> Option: QO Enter/edit quick orders Select QUICK ORDER NAME: TEST CID PROMPT NAME: TEST CID PROMPT Replace DISPLAY TEXT: TEST CID PROMPT// VERIFY ORDER: YES// DESCRIPTION: No existing text Edit? NO// ENTRY ACTION: Procedure: ERCP// Service: GASTROENTEROLOGY// Reason for Request: No existing text Edit? No// (No) Category: OUTPATIENT// Urgency: ROUTINE// Clinically indicated date:7 DAYS FROM TODAY// <-- UPDATED VALUE NOTE: The report logic can determine if OR*3.0*350/CPRS GUI v30.B has been installed. If not, the report will build data based on the EARLIEST DATE field. If 30.B has already been installed, the report can build data off the CLINICALLY INDICATED DATE field. If the post-install routine ORY389 is left on the system, the report can be re-run any time by executing the following line from the programmer prompt: D CONSULT^ORY389 ======================================================================== ========CREATING CLINIC QUICK ORDERS FROM INPATIENT QUICK ORDERS======== ======================================================================== A new quick order conversion utility has been added to the ORDER MENU MANAGEMENT menu [ORCM MGMT]. Create Clinic Order QOs from Inpatient QOs [OR CONV INPT QO TO CLIN ORD QO] is a utility that can convert certain inpatient medication quick orders into clinic quick orders. Specifically, Unit Dose quick orders can be converted to Clinic Medication quick orders and IV Medication quick orders can be converted to Clinic Infusion quick orders. The utility offers two actions to choose from when converting a quick order: Copy or Move. Copy will create a copy of the quick order and then, if OR*3.0*350 (CPRS GUI v30.B) has been installed, will prompt you to delete the originally selected quick order. During the copy process, the user is prompted to enter a new name for the copied order and the Display Group is set to Clinic Medications. The Copy action can only work with one quick order at a time and therefore is limited to a single selection item from the list of available quick orders. If you choose to delete the original quick order, the utility will check for any pointers referencing the selected quick order. If any other items (menus, order sets, display group(s), reminder dialog items) are referencing the selected quick order, the delete action will not be permitted. If any pointers are found, the utility will display those items on the screen. If, at some point in the future, the pointers are removed (i.e. you find that the selected QO is part of an order menu and then you remove that QO from the menu) you should then be able to manually delete the QO via the QO editor [ORCM QUICK ORDERS]. Move will modify the selected quick order by changing the Display Group to Clinic Medications or Clinic Infusions. The Move action allows for selecting either a single item or a range of items (e.g. 1,3,4-9) to be converted in succession. Patch Components: ================================================================= Files & Fields Associated: ================================================================= File Field New/Modified/Deleted ------------------------------------------------------------------ ORDER (#100) DIALOG (#2) Modified ORDER (#100) ITEM ORDERED (#7) Modified Forms Associated: ================= N/A Mail Groups Associated: ======================= N/A Options Associated: =================== ORCM MGMT Modified OR CONV INPT QO TO CLIN ORD QO New OR CONVERT UD TO CM Delete Protocols Associated: ===================== N/A Security Keys Associated: ========================= N/A Templates Associated: ===================== N/A Additional Information: ======================= N/A New Service Requests (NSRs): ============================ N/A Patient Safety Issues (PSIs): ============================= N/A Remedy Ticket(s) & Overview: ============================ N/A Test Sites: =========== Cleveland, OH Heartland - East Heartland - West Loma Linda, CA Palo Alto, CA San Diego, CA Pre/Post Installation Overview: =============================== The patch does not contain any pre-install activity. Post-install creates two tasked jobs. The first will create the new cross-references in the ORDER file (#100). The second will compile a list of all consult quick orders and the stored value for the Earliest Appropriate Date field. When complete, each job sends a mail message to the installer and/or selected recipients. 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_389

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: 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))#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))#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/master/Packages/Inpatient+Medications/Patches/PSJ_5.0_323

Patch Subject: ENTERPRISE HEALTH MANAGEMENT PLATFORM Description: ============ ENTERPRISE HEALTH MANAGEMENT PLATFORM (eHMP) The eHMP project within the Veterans Health Information Systems and Technology (VistA) Evolution program will introduce expanded capabilities and modernize existing features of the VA VistA Electronic Health Record (EHR) system. The eHMP project is a multi-year effort to evolve a modern, service-oriented Enterprise Health Application Platform. This platform includes VistA Exchange, the eHMP graphical user interface (GUI), as well as clinical knowledge enrichment and decision support services. VistA Exchange is the clinical data services engine, federating clinical data from a variety of VA and DoD sources into an Enterprise Health Management Platform Patient Record. The eHMP framework will incorporate capabilities currently provided by Joint Legacy Viewer (JLV) and Health Informatics Initiative (hi2) HMP. The eHMP will eventually replace the Computerized Patient Record System (CPRS) as VA's primary point of care application. The eHMP Viewer Edition version 1.2 is the initial product providing a user interface. This project is being deployed in phases with each iteration adding new features. ***Note*** eHMP will be a phased implementation To see the current status and target dates for Sites/VISN/Regions please refer to the following site: http://vaww.oed.portal.domain.ext/pm/iehr/vista_evolution/ehmpdeployment/eHMP% 20v12/Forms/All%20Items.aspx?RootFolder=/pm/iehr/vista_evolution/ehmpdeplo yment/eHMP%20v12/Resources/Waves%20and%20Timelines Patch Components ================ This release contains an HMP Prerequisite Bundle and Hmp 2.0 KIDs build. The order of installation will be the prerequisite bundle KID file followed by the HMP 2.0 KID file. ***Note*** The pre-requisite, multi-build patch that contains all the patches needed prior to installation of the HMP 2.0 patch. The multi-build contains the following: GMRC*3.0*80 MD*1.0*38 OR*3.0*390 PSB*3.0*79 TIU*1.0*106 TIU*1.0*298 USR*1.0*37 HMP 2.0 The following sections are specific to the HMP 2.0 patch, which is the primary patch for eHMP. The patches in the prerequisite bundle contain methods for extracting domain specific data to the eHMP User Interface (UI) and the JavaScript Object Notation (JSON) Data Store. Files & Fields Associated: -------------------------- The following new files are exported with this patch: File Name (#) Field Name (#) New/Modified/Deleted ------------- -------------- -------------------- HMP SUBSCRIPTION (#800000) New SERVER (#.01) LASTUPDATE (#.02) OPERATION DATA (#.03) REPEAT POLLS (#.04) DISK USAGE STATUS (#.05) DISK USAGE STATUS TIME (#.06) URL (#.1) PATIENT (#1) MULTIPLE PATIENT NAME (#.01) STATUS (#2) STATUS DATE-TIME (#3) ORDERS (#4) MULTIPLE ORDER NUMBER (#.01) CREATE DATE/TIME (#.02) SIGNED BY (#.03) SIGNED DATE/TIME (#.04) VERIFYING NURSE (#.05) NURSE VERIFY DATE/TIME (#.06) VERIFYING CLERK (#.07) CLERK VERIFY DATE/TIME (#.08) REVIEWED BY (#.09) REVIEWED DATE/TIME (#.1) RELEASED BY (#.11) RELEASED DATE/TIME (#.12) PURGE DATE/TIME (#.13) ORDER ACTION (#.14) ACTION DATE/TIME (#.15) TRACKING START (#1.01) ORDER FLAG/UNFLAG DATE/TIME (#2) MULTIPLE ORDER FLAG/UNFLAG DATE/TIME (#.01) FLAG ACTION (#.02) FLAG/UNFLAG USER (#.03) FLAG/UNFLAG REASON (#.04) ROSTER (#2) MULTIPLE NAME (#.01) ON (#2) CONCURRENT UPDATE CALLS (#91) HMP PATIENT OBJECT (#800000.1) New UID (#.01) PATIENT (#.02) COLLECTION (#.03) DATA (#1) MULTIPLE DATA (#.01) HMP OBJECT (#800000.11) New UID (#.01) COLLECTION (#.03) DATA (#1) MULTIPLE DATA (#.01) HMP LIST (#800000.2) New NAME (#.01) TYPE (#.02) DD NUMBER (#.03) DOMAIN (#.04) ATTRIBUTE (#.05) REFRESH THRESHOLD (#.08) NEXT REFRESH DATE (#.09) GENERATION CODE (#11) COLUMNS (#.2) MULTIPLE COLUMN NAME (#.01) ORDER (#.02) DESCRIPTION (#.3) MULTIPLE DESCRIPTION (#.01) DATA (#.9) MULTIPLE DATA (#.01) HMP LIST DOMAIN (#800000.21) New NAME (#.01) ABBREVIATION (#.02) DISPLAY NAME (#.03) HMP LIST ATTRIBUTE (#800000.22) New NAME (#.01) ABBREVIATION (#.02) DISPLAY NAME (#.03) HMP PANEL (#800001) New NAME (#.01) DISPLAY NAME (#.02) PATIENT LIST NAME (#.03) ORDER DIALOGS (#5) MULTIPLE ORDER DIALOGS (#.01) HMP ROSTER (#800001.2) New NAME (#.01) DISPLAY NAME (#.02) DISABLE (#.03) OWNER (#.04) TYPE (#.05) PATIENT LIST NAME (#.06) SOURCES (#1) MULTIPLE SEQUENCE (#.01) SOURCE (#.02) OPERATION (#.03) FILTER (#.04) REFRESH FREQUENCY (#.05) SPECIAL HANDLING (#2) PATIENT (#3) MULTIPLE PATIENT (#.01) SRCSEQ (#.02) TIMESTAMP (#99) HMP ACTIVITY (#800001.5) New PATIENT NAME (#.01) APPOINTMENT DATE (#2) APPOINTMENT STATUS (#3) DATE RECORD CREATED (#4) DATE RECORD RETREIVED (#5) HMP PROCESS FLAG (#6) JSON MESSAGE (#7) Checksums: ---------- The checksums were calculated using CHECK1^XTSUMBLD. HMP*2.0*0 ENTERPRISE HEALTH MANAGEMENT PLATFORM HMP0311P value = 14101699 HMP0311Q value = 3902876 HMPACT value = 34386179 HMPAT value = 3595282 HMPCAC value = 97070146 HMPCORD4 value = 141593321 HMPCORD5 value = 89350961 HMPCPRS value = 5087431 HMPCRPC value = 13274810 HMPCRPC1 value = 103567295 HMPD value = 29605922 HMPDCRC value = 46986534 HMPDERRH value = 2044240 HMPDGMPL value = 28172327 HMPDGMRA value = 22211624 HMPDGMV value = 43285050 HMPDJ value = 36572187 HMPDJ0 value = 118417079 HMPDJ00 value = 150294972 HMPDJ01 value = 49806712 HMPDJ02 value = 178043401 HMPDJ03 value = 97739485 HMPDJ04 value = 86219849 HMPDJ04A value = 59768993 HMPDJ04E value = 18074806 HMPDJ05 value = 85682186 HMPDJ05V value = 69065747 HMPDJ06 value = 64037338 HMPDJ07 value = 26955013 HMPDJ08 value = 73570854 HMPDJ08A value = 50353978 HMPDJ09 value = 47251770 HMPDJ09M value = 14316939 HMPDJ1 value = 18644090 HMPDJ2 value = 21439862 HMPDJFS value = 74871558 HMPDJFS1 value = 1887278 HMPDJFSD value = 6635230 HMPDJFSG value = 216382035 HMPDJFSM value = 91943836 HMPDJFSP value = 228347665 HMPDJX value = 36089287 HMPDLR value = 24262347 HMPDLRA value = 79686061 HMPDMC value = 58181283 HMPDMDC value = 45041787 HMPDOR value = 13574723 HMPDPSOR value = 2311665 HMPDRA value = 42792632 HMPDSDAM value = 21275067 HMPDSR value = 30022036 HMPDTIU value = 83859727 HMPDVSIT value = 93496568 HMPEASU value = 29036042 HMPEF value = 86254671 HMPEF1 value = 36268404 HMPEFX value = 8398930 HMPEHL7 value = 3570530 HMPELAB value = 7483676 HMPEQ value = 27101202 HMPEQLM value = 113676837 HMPEQLM1 value = 7071509 HMPEQLM2 value = 3277771 HMPEVNT value = 129413290 HMPFPTC value = 15382684 HMPHTTP value = 14631122 HMPIDX value = 2980358 HMPJSON value = 11632331 HMPJSOND value = 71688388 HMPJSONE value = 27506711 HMPLIST value = 62846538 HMPMDUTL value = 53381465 HMPMETA value = 122279349 HMPP3I value = 129333471 HMPPARAM value = 16541840 HMPPATS value = 3116859 HMPPDL value = 23790480 HMPPRXY2 value = 16933808 HMPPTDEM value = 12665908 HMPPXRM value = 14531240 HMPROS8 value = 82143309 HMPSTMP value = 70461106 HMPTFU2 value = 40086168 HMPTOOLS value = 11387818 HMPUPD value = 25123694 HMPUTIL1 value = 42764058 HMPUTILS value = 39059234 HMPXGDPT value = 2019789 HMPXGLAB value = 1064430 HMPXGNP value = 1299808 HMPXGORD value = 2568884 HMPXGSD value = 2602100 HMPYCSO value = 22000106 HMPZ0218 value = 5632129 MD*1.0*38 CLINICAL PROCEDURES Routine Before After 2nd Line MDCPROTD New 6754694 **38** MDPOST38 New 2283064 **38** OR*3.0*390 ORDER ENTRY/RESULTS REPORTING Routine Before After 2nd Line ORCACT1 49420108 50018442 **7,27,56,48,86,92,116,149,215, 284,390** ORCSEND 65578810 66459073 **4,27,45,79,92,141,165,195, 228,243,303,296,390** ORMBLDOR 2239296 5850168 **97,390** ORWDXA 82710229 83747347 **10,85,116,132,148,141,149, 187,213,195,215,243,280,306, 390** PSB*3.0*79 BAR CODE MED ADMIN Routine Before After 2nd Line PSBML 127507803 134214064 **6,3,4,9,11,13,25,45,33,52, 70,72,79** PSBVPR New 2149221 **79** TIU*1.0*106 TEXT INTEGRATION UTILITIES Routine Before After 2nd Line TIUDDX New 292958 **106** TIUPS106 New 3258435 **106** TIUVPR New 11093980 **106** GMRC*3.0*80 CONSULT/REQUEST TRACKING Routine Before After 2nd Line GMRCAPI New 8359535 **80** USR*1.0*37 AUTHORIZED SUBSCRIPTION UTILITY Routine Before After 2nd Line USRCLASS 11828621 14942098 **7,11,33,37** USRRULA 24614630 28762260 **3,28,29,37** TIU*1.0*298 TEXT INTEGRATION UTILITIES There are no routines in this patch. Forms Associated: ----------------- There are no new or modified forms. Mail Groups Associated: ----------------------- HMP IRM GROUP - This mail group will receive alerts from the eHMP subscription process if the usage of global ^XTMP reaches the limit allowed and begins to pause subscriptions until disk space is available. The mail group also receives notifications when disk space is freed up and subscriptions are again proceeding. The eHMP software automatically clears the ^XTMP data after it is processed. Options Associated: ------------------- The following new options are associated with this release: - HMP Application Proxy [HMP APPLICATION PROXY] - This option allows the HMP connector proxy access to the VistA system. - Return List of Tomorrow's Patients [HMP APPOINTMENTS] - This option should be scheduled to run nightly, to notify the Enterprise Health Management Platform (eHMP) of patients that are to be seen tomorrow. - XTMP Global Monitor [HMP MONITOR FOR XTMP GLOBAL] - This option will monitor amount of space in the ^XTMP global used by the eHMP. The amount used is very dynamic - Patient Appointments [HMP PATIENT ACTIVITY] - Return appointments for a subscribed patient. - HMP Patient Data Monitor [HMP PATIENT DATA MONITOR] - This option manages the HMP Patient Data Monitor background job. It first checks to see if the job is running, and will prompt the user to start it if it's stopped. It may also be used to stop the job, but the eHMP client may not display up-to-date data until it is started up again. - Synchronize the HMP [HMP SYNCHRONIZATION CONTEXT]- This option manages access to RPCs responsible for synchronization of eHMP data with VistA. - HMP UI Context Version 0.7-S62 [HMP UI CONTEXT] - This option allows the HMP UI access to the VistA system. - Writeback Of Domain Data To VistA [HMP WB DOMAINS] - Writes domain data to VistA - HMP Writeback Patient Demographics [HMP WB PTDEM] - This option allows eHMP to change patient phone numbers in VistA. - New Person events for HMP [HMP XU EVENTS] - This protocol will track New Person updates for HMP. - Manually Add Patient to HMP [HMPM ADD HMP PATIENT] - Use this option to manually add a patient for synchronization with the Enterprise Health Management Platform (eHMP). - Add Health Management Platform User [HMPM ADD HMP USER] - This option allows a user to be given access to use the Health Management Platform. The selected user will be given the HMP UI CONTEXT option. Additionally, their default patient list may be set up for automatic synchronization with the Health Management Platform (HMP). - Emergency Stop HMP Freshness Updates [HMPM EMERGENCY STOP] - This option should be used with caution. It will stop the freshness events for the ENTERPRISE HEALTH MANAGEMENT PLATFORM (HMP) from being called. Once the freshness events are stopped, patient data must be re-synchronized with the HMP to ensure completeness. Only stop freshness updates if there is a problem with system operation. - Monitor HMP Server Synchronization [HMPM EXTRACT MONITOR] - This option is used to monitor the polls from an HMP server and any currently executing HMP extracts. - Resume Freshness Updates That Have Been Stopped [HMPM RESTART FRESHNESS] - This option will remove the flags that cause freshness updates to be stopped. It will likely be necessary to re-synchronized patients after freshness has been stopped, since updates will be missing from the time that freshness updates were not being received. - HMP Technical Management [HMPMGR] - This menu contains various options to help with the management of HMP Parameter Definitions: ---------------------- The following new Parameter Definitions were added to the PARAMETER DEFINITION file (#8989.51). These parameters should not be modified. HMP CPRS PATH HMP DOMAIN SIZES HMP EXTRACT DISK SIZE LIMIT HMP EXTRACT TASK REQUEUE SECS HMP JSON SCHEMA HMP LOCATIONS HMP PARAMETERS HMP SYSTEM NAME HMP TASK WAIT TIME HMP VERSION Protocols Associated: --------------------- The following new or modified Protocols are included in this KID build. Protocol Name New/Modified/Deleted ------------- -------------------- HMP ADT-A04 CLIENT New HMP ADT-A08 CLIENT New HMP APPT EVENTS New HMP DG UPDATES New HMP DGPF ASSIGN FLAG New HMP GMPL EVENT New HMP GMRA EVENTS New HMP INPT EVENTS New HMP MDC EVENT New HMP NA EVENTS New HMP PCE EVENTS New HMP PCMM TEAM New HMP PCMM TEAM POSITION New HMP PSB EVENTS New HMP XQOR EVENTS New HMPM EVT QUE CHANGE DOMAIN New HMPM EVT QUE CHANGE MAX LISTED New HMPM EVT QUE CHANGE SERVER New HMPM EVT QUE DISPLAY DETAILS New HMPM EVT QUE FILTER New HMPM EVT QUE FRESHNESS REPORT New HMPM EVT QUE MGR MENU New HMPM EVT QUE REFRESH New HMPM EVT QUE SELECT PATIENT New HMPM EVT QUE SHOW TEMP GLOBALS New DG FIELD MONITOR Modified DGPM MOVEMENT EVENTS Modified FH EVSEND OR Modified GMPL EVENT Modified GMRA ENTERED IN ERROR Modified GMRA SIGN-OFF ON DATA Modified GMRC EVSEND OR Modified LR7O CH EVSEND OR Modified MDC OBSERVATION UPDATE Modified OR EVSEND FH Modified OR EVSEND GMRC Modified OR EVSEND LRCH Modified OR EVSEND ORG Modified OR EVSEND PS Modified OR EVSEND RA Modified OR EVSEND VPR Modified PS EVSEND OR Modified PSB EVSEND VPR Modified PXK VISIT DATA EVENT Modified RA EVSEND OR Modified SCMC PATIENT TEAM CHANGES Modified SCMC PATIENT TEAM POSITION CHANGES Modified SDAM APPOINTMENT EVENTS Modified Remote Procedure Calls (RPCs) ----------------------------- The following new RPCs are included with this installation HMP APPOINTMENTS HMP CHKXTMP HMP DATA VERSION HMP DEFAULT PATIENT LIST HMP DELETE OBJECT HMP DELETE ROSTER HMP GET CHECKSUM HMP GET OBJECT HMP GET OPERATIONAL DATA HMP GET PATIENT DATA HMP GET PATIENT DATA JSON HMP GET REFERENCE DATA HMP GET ROSTER LIST HMP GET SOURCE HMP GLOBAL SIZE HMP INPATIENTS HMP LOCAL CORRESPONDINGIDS HMP LOCAL GETCORRESPONDINGIDS HMP PATIENT ACTIVITY HMP PATIENT ADMIT SYNC HMP PATIENT SCHED SYNC HMP PREVIEW ROSTER HMP PUT DEMOGRAPHICS HMP PUT OBJECT HMP PUT OPERATIONAL DATA HMP PUT PATIENT DATA HMP ROSTER PATIENTS HMP ROSTERS HMP SUBSCRIBE HMP SUBSCRIBE ROSTERS HMP UPDATE ROSTER HMP WRITEBACK PT DEM HMPCORD RPC HMPCPAT RPC HMPCPRS RPC HMPCRPC RPC HMPCRPC RPCCHAIN HMPDJFS API HMPDJFS DELSUB HMPFPTC CHKS HMPFPTC LOG Security Keys Associated: ------------------------- HMP ADMIN - This key is used to determine which HMP users should be allowed to manage subscriptions and the subscription queue. HMP EXPERIMENTAL - This key is used to isolate new features for site testing. Templates Associated: --------------------- HMPM EVT QUE MGR - List Template HL7 Application Parameter: ========================== HMP HL7 New Service Requests (NSRs): ----------------------------- NSR #20150408 - VistA Evolution Enterprise Health Management Platform (eHMP) Patient Safety Issues (PSIs): ------------------------------ There are no PSIs addressed in this patch Remedy Ticket(s) & Overviews: ----------------------------- There are no Remedy Tickets addressed in this patch Test Sites: ----------- Hampton, VA Portland, OR San Diego, CA Loma Linda, CA San Antonio, TX Software and Documentation Retrieval Instructions: -------------------------------------------------- This is PHASED IMPLEMENTATION. The host files and instructions will be provided by ASMR/eHMP Implementation Team based on the implementation Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Enterprise+Health+Management+Platform/Patches/HMP+2.0

Patch Subject: REGISTRATION CAMP LEJEUNE ELIGIBILITY UPDATE Description: ============ ************************************************************************** This patch is being released in support of the Camp Lejeune - Veterans project. DG*5.3*909 (Registration) is being released along with IVM*2*161 (Income Verification Match) in host file: DG_5_3_P909.KID. It is imperative that these patches be installed no later than the compliance date. Your understanding and support is appreciated. ************************************************************************** Public Law 112-154, requires Veterans Affairs (VA) to provide hospital care and medical services to Veterans who served on active duty at Camp Lejeune (North Carolina) for one or more of 15 specified illnesses or conditions (Esophageal cancer; Lung cancer; Breast cancer; Bladder cancer; Kidney cancer; Leukemia; Multiple myeloma; Myelodysplastic syndromes; Renal toxicity; Hepatic steatosis; Female infertility; Miscarriage; Scleroderma; Neurobehavioral effects; or Non-Hodgkin's lymphoma). To be eligible for care under the provisions of this bill, the Veteran must have served on active duty at Camp Lejeune for not fewer than thirty (30) consecutive or nonconsecutive days between August 1, 1953 and December 31, 1987. The Camp Lejeune - Veterans (CL-V) project will update VistA to allow for the accurate tracking of veterans who satisfy the CL-V eligibility requirements and are therefore entitled to these additional benefits. This patch modifies the Registration v5.3 application as described below: 1. Adds the following fields to the PATIENT (#2) file for storing the Camp Lejeune data: -CAMP LEJEUNE (#.321701) field - Updated by VistA users or by processing an ORF-Z11 or ORU-Z11 message from ES containing Camp Lejeune data. Values are Null (Blank), YES or NO. Once the field contains a YES or NO value, it cannot be set back to Null. -CAMP LEJEUNE DATE (#.321702)- Updated by the system when the CAMP LEJEUNE (#.321701) field is updated. -CAMP LEJEUNE CHANGE SITE (#.321703) - Updated by the system when the CAMP LEJEUNE (#.321701) field is updated. -CAMP LEJEUNE SOURCE (#.321704) - Updated by the system when the CAMP LEJEUNE (#.321701) field is updated. -CAMP LEJEUNE DATA ENTRY LOCKED (#.32171) - Updated by the system when an ORF-Z11 or ORU-Z11 message processes Camp Lejeune data. Values are "1" for LOCKED, "0" for NOT LOCKED. 2. Adds the following fields to the PATIENT ENROLLMENT (#27.11) file for storing the Camp Lejeune data: -CAMP LEJEUNE INDICATED? (#50.24) - Updated by the system when the CAMP LEJEUNE (#.321701) field is updated. Values are Null (Blank),YES or NO. -CAMP LEJEUNE DATE (#50.25) - Updated by the system when the CAMP LEJEUNE (#.321701) field is updated. -CAMP LEJEUNE CHANGE SITE (#50.26) - Updated by the system when the CAMP LEJEUNE (#.321701) field is updated. -CAMP LEJEUNE SOURCE (#50.27) - Updated by the system when the CAMP LEJEUNE (#.321701) field is updated. 3. Allows editing of CL-V data on the MILITARY SERVICE DATA, SCREEN <6> Environmental Factors sub-screen. Related Options: Register a Patient [DG REGISTER PATIENT] Load/Edit Patient Data [DG LOAD PATIENT DATA] Eligibility Verification [DG ELIGIBILITY VERIFICATION] Admit a Patient [DG ADMIT PATIENT] The following menu option allows the VistA user access to view CLE in the Environmental Factors screen: View Registration Data [DG REGISTRATION VIEW] The following menu option allows the VistA user access to view CLE in the Patient Enrollment screen: Patient Enrollment [DGEN PATIENT ENROLLMENT] The environmental sub screen has been updated to display a new environmental factor for Camp Lejeune. This new factor will be the 5th in the list as shown below. LASTNAME,FIRSTNAME; XXX-XX-XXXX ------------------------------------------------------------------------- **** ENVIRONMENTAL FACTORS **** [1] A/O Exp.: Reg: Exam: A/O#: [2] ION Rad.: Reg: Method: [3] SW Asia Cond: Reg: Exam: [4] N/T Radium: [5] Camp Lejeune: SELECT AN ENVIRONMENTAL FACTOR (1-5) OR (Q)UIT: QUIT// VistA will enable the Camp Lejeune environmental factor for editing if all of the following CLE rules are met: - Person is a Veteran AND - Person has one or more Military Service Episode(s) (MSE) that include no less than 30 days of service between August 1, 1953 and December 31, 1987 (inclusive) AND - All of the identified MSE(s) used for the 30-day service duration has a character of discharge other than: - Dishonorable - Other Than Honorable - Undesirable - Bad Conduct - Dishonorable-VA (See Note *) If multiple Military Service Episodes (MSEs) are used to count the 30-day service duration requirement, the MSEs do not have to be consecutive days. - If a primary eligibility code exists, it must be a Veteran eligibility code as follows: - Service Connected 50% to 100%. - SC Less than 50% - Prisoner of War - Purple Heart Recipient - Aid & Attendance - Housebound - NSC, VA Pension - World War I - NSC - The CAMP LEJEUNE DATA ENTRY LOCKED (#.32171) field in the PATIENT (#2) file has not been set by uploading the CL-V data from an ORF-Z11 or ORU-Z11 HL7 message received from ES. If the veteran does not satisfy the Camp Lejeune eligibility requirements, option five will be surrounded by pointed brackets <5> and will not be selectable. Note: The View Registration Data [DG VIEW REGISTRATION] option is read only. Number five on the ENVIRONMENTAL FACTORS screen will be surrounded by pointed brackets <5> and will not be selectable. LASTNAME,FIRSTNAME; XXX-XX-XXXX ------------------------------------------------------------------------- **** ENVIRONMENTAL FACTORS **** [1] A/O Exp.: Reg: Exam: A/O#: [2] ION Rad.: Reg: Method: [3] SW Asia Cond: Reg: Exam: [4] N/T Radium: <5> Camp Lejeune: SELECT AN ENVIRONMENTAL FACTOR (1-5) OR (Q)UIT: QUIT// 4. Displays Camp Lejeune on the MILITARY SERVICE DATA, SCREEN <6> for Environmental Factors when the Camp Lejeune indicator on the ENVIRONMENTAL FACTORS sub-screen displays YES. MILITARY SERVICE DATA, SCREEN <6> LASTNAME,FIRSTNAME; XXX-XX-XXXX SC VETERAN ========================================================================= [1] Service Branch/Component Service # Entered Separated Discharge ------------------------ --------- ------- --------- --------- ARMY/REGULAR XXXXXXXXX 02/20/1958 03/01/1969 HONORABLE [2] Conflict Locations: < None Specified > [3] Environment Factors: (5) Camp Lejeune [4] POW: From: To: War: [5] Combat: From: To: Loc: [6] Mil Disab Retirement: Dischrg Due to Disab: [7] Dent Inj: Teeth Extracted: [8] Purple Heart: LASTNAME,FIRSTNAME; XXX-XX-XXXX ========================================================================== **** ENVIRONMENTAL FACTORS **** [1] A/O Exp.: Reg: Exam: A/O#: [2] ION Rad.: Reg: Method: [3] SW Asia Cond: Reg: Exam: [4] N/T Radium: [5] Camp Lejeune: YES 5. Flags a Veteran's record for transmission to ES. When a VistA user enters or updates the Camp Lejeune indicator, the record will be flagged for transmission and sent to the Enrollment System the next time the IVM Background Job completes. ES will process the CL-V data and make an enrollment determination, generating an ORU-Z11 to all VistA sites of interest. When VistA processes the ORU-Z11 with the Camp Lejeune data in VistA, the CAMP LEJEUNE DATA ENTRY LOCKED (#.32171) field in the PATIENT (#2) file will be set to "1" for "LOCKED" and the Camp Lejeune indicator will no longer be editable within VistA. From this point forward, the Camp Lejeune option five will appear with the pointed brackets <5> and all future updates to the CL-V data will need to be coordinated through the Health Eligibility Center (HEC) via the HEC Alert process. 6. Adds help text. When the Camp Lejeune environmental factor is selected, the user receives the prompt "CAMP LEJEUNE WATER CONTAMINANT EXPOSURE INDICATED?//". The user may solicit help by entering double question marks "??" at the prompt. The following help text will display: SELECT AN ENVIRONMENTAL FACTOR (1-5) OR (Q)UIT: QUIT// 5 Camp Lejeune CAMP LEJEUNE WATER CONTAMINANT EXPOSURE INDICATED?//?? Enter "Y" if veteran claims need for care of conditions related to exposure of "Water Contamination at Camp Lejeune". Enter "N" if veteran was not assigned to Camp Lejeune between August 1, 1953 and December 31, 1987 or does not claim need for care of conditions related to exposure of "Water Contamination at Camp Lejeune". Choose from: Y YES N NO Null "Blank" 7. Displays CL-V data on the Patient Enrollment Screen. Related Option: Patient Enrollment [DGEN PATIENT ENROLLMENT] The Camp Lejeune data is added to Page 2 of the Patient Enrollment screen, directly below the SW Asia Cond display. This is a display only screen and no editing of the Camp Lejeune data is allowed. The SW Asia Cond display prompt is modified to display a colon rather than a period and align properly. The following is an example of the updated screen display: Patient Enrollment Dec 03, 2014@14:37:55 Page: 2 of 4 Patient: PATIENT,TEST (1111) NSC VETERAN Preferred Facility: ALBANY Current Enrollment Preferred Facility Source: VISTA + Priority Factors POW: NO Purple Hrt: A/O Exp.: YES A/O Exp Loc: KOREAN DMZ ION Rad.: YES Rad Exp Method: OTHER SW Asia Cond: YES Camp Lejeune: Mil Disab Retirement: Dischrg Due to Disab: Combat Vet End Date: Eligible for MEDICAID: Svc Connected: NO SC Percent: + Query: TRANSMITTED Notify: EP (Enroll Patient) QS Check Query Status SP Select Patient PF Preferred Facility SQ (Send Query) AU (View Upload Audit) EH Expand History CD Catastrophic Disab. PZ Print 1010EZ/EZR Select Action:Next Screen// 8. Modifies the initial enrollment determination algorithm to place CL-V eligible Veterans in priority group 6 unless a higher priority is determined based on other eligibility factors. No changes were made to continuous enrollment rules in VistA. CL-V eligible Veterans are subject to means testing and/or Rx copay testing, unless other eligibility factors make them income testing exempt. 9. Updates the ORF-Z11 and ORU-Z11 receivers to process the CL-V data sent from ES in ZEL segment sequences 41 through 44. Segment HL7 Element Name VistA Stored Field - File Location - Sequence ZEL-41 CAMP LEJEUNE CAMP LEJEUNE INDICATED? (#50.24) field PATIENT ENROLLMENT (#27.11) file CAMP LEJEUNE (#.321701) field PATIENT (#2) file ZEL-42 CAMP LEJEUNE DATE CAMP LEJEUNE DATE (#50.25) field PATIENT ENROLLMENT (#27.11) file CAMP LEJEUNE DATE (#.321702)field PATIENT (#2) file ZEL-43 CAMP LEJEUNE CHANGE SITE CAMP LEJEUNE CHANGE SITE (#50.26) field PATIENT ENROLLMENT (#27.11) file CAMP LEJEUNE CHANGE SITE (#.321703) field PATIENT (#2) file ZEL-44 CAMP LEJEUNE SOURCE CAMP LEJEUNE SOURCE (#50.27) field PATIENT ENROLLMENT (#27.11) file CAMP LEJEUNE SOURCE (#.321704) field PATIENT (#2) file Patch IVM*2.0*161 will be released in conjunction with this REGISTRATION patch. Patch Components ================ Files & Fields Associated: File Name (#) Field Name (#) New/Mod/Del ------------- ---------------------------------------- ----------- PATIENT (#2) CAMP LEJEUNE (#.321701) New CAMP LEJEUNE DATE (#.321702) New CAMP LEJEUNE CHANGE SITE (#.321703) New CAMP LEJEUNE SOURCE (#.321704) New CAMP LEJEUNE DATA ENTRY LOCKED (#.32171) New PATIENT ENROLLMENT (#27.11) CAMP LEJEUNE INDICATED? (#50.24) New CAMP LEJEUNE DATE (#50.25) New CAMP LEJEUNE CHANGE SITE (#50.26) New CAMP LEJEUNE SOURCE (#50.27) New Forms Associated: Form Name File # New/Mod/Del --------- ------ ----------- N/A Mail Groups Associated: Mail Group Name New/Mod/Del --------------- ----------- N/A Options Associated: Option Name Type New/Mod/Del ----------- ---- ----------- N/A Protocols Associated: Protocol Name New/Mod/Del ------------- ----------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (#) New/Mod/Del ------------- ---- ------------------ ----------- N/A Additional Information: ICR-3812 was updated to include information on the new CL-V data fields that were added to the output array DGENR. DGENR("ELIG","CLE")="Y" DGENR("ELIG","CLEDT")=3150220 DGENR("ELIG","CLESOR")="VAMC" DGENR("ELIG","CLEST")=500 New Service Requests (NSRs): ----------------------------- 20120809 Patient Safety Issues (PSIs): ------------------------------ N/A Remedy Ticket(s) & Overviews: ----------------------------- N/A Test Sites: ----------- VA Pittsburgh Health Care System Erie VA Medical Center Altoona - James E. VanZandt VA Medical Center 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 SFTP Mode -------------------------------------------------------------------------- PIMS User Manual - ADT Module DG_5_3_P909_ADTBE_UM.PDF (binary) User Manual - Registration Menu DG_5_3_P909_REG_UM.PDF (binary) IVM Technical Manual IVM_2_P161_TM.PDF (binary) CL-V VistA REE Release Notes CL-VVISTA_REERELEASENOTES.PDF (binary) SFTP Instructions: ------------------ CL-V includes the following patches. The host file was created to simplify installation at Veterans Health Administration (VHA) facilities. File Name Contents Retrieval Format -------------------------------- ----------- ---------------- DG_5_3_P909.KID DG*5.3*909 ASCII IVM*2.0*161 Patch Installation: Pre/Post Installation Overview ------------------------------ N/A Use default answers for KIDS load/install questions. Multi-Build: http://code.osehra.org/VistA.git/blob/master/Packages/MultiBuilds/DG_5_3_P909.KID Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Income+Verification+Match/Patches/IVM_2.0_161

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 #1 Routines DPTLK4 and DPTLK7 were updated so that the WHO ENTERED PATIENT field (#.096) in the PATIENT file (#2) is populated for new patients registered with the REGISTER A PATIENT [DG REGISTER PATIENT] menu option. Issue #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 (#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 (#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 (#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/master/Packages/Registration/Patches/DG_5.3_919

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: 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: 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: VISTA SCHEDULING ENHANCEMENT E1-E2 Description: ============ ***************************** PLEASE NOTE ******************************** * * *The VHA Release Board has NOT provided approval for this patch to be * * installed in ANY production environment. * * * * NOTE: This patch is ONLY to be loaded into a TEST environment until * * approval from the VHA Release Board is obtained to load into facility * * production environments. * * * ************************************************************************** The Veterans Health Administration (VHA) Access and Clinic Administrative Program (ACAP) has requested an enterprise enhancement for the VistA Scheduling Package. The enhancement will reduce operating cost for VHA and improve operational efficiencies resulting in patient centered access to care, coordinated care, increased customer satisfaction, and the reduction of excessive cycle/wait time used for scheduling patients. The following patches along with VS GUI v2.0.0.5 provide a VistA Scheduling (VS) Graphical User Interface (GUI) for the Patient Information Management Systems (PIMS) Scheduling package: GMRC*3.0*83 SD*5.3*627 (This patch) SD*5.3*628 SD*5.3*643 SD*5.3*642 SD*5.3*645 Note: The patches noted above are to be installed in the order listed except for SD*5.3*645 which is a standalone patch and can be installed at any time. ************************************************************************** * PLEASE TAKE NOTE OF THE FOLLOWING CHANGE * * * * The option 'Multiple CLinic Display/Booking' [SDMULTICLINIC] must be * * disabled because it is not compatible with the changes distributed in * * this patch. OI&T must use 'Edit Options' under 'Menu Management' in * * EVE to mark [SDMULTICLINIC] as 'Out of Order'. * * * ************************************************************************** Patch Components ================ Files & Fields Associated: File Name (#) Field Name (#) NEW/MODIFIED/DELETED ------------- -------------- -------------------- HOSPITAL LOCATION NAME Modified (#44) (#.01) HOSPITAL LOCATION TYPE Modified (#44) (#2) PRIVILED USER SUB-FILE PRIVILEGED USER Modified (#44.04) (#.01) PROVIDER SUB-FILE PROVIDER Modified (#44.1) (#.01) RECALL REMINDERS USER WHO ENTERED RECALL Modified (#403.5) (#7) RECALL REMINDERS DATE/TIME RECALL ADDED New (#403.5) (#7.5) RECALL REMINDERS REMOVED USER WHO ENTERED RECALL Modified (#403.56) (#7) RECALL REMINDERS REMOVED DATE/TIME RECALL ADDED New (#403.56) (#7.5) SD WAIT LIST ORIGINATING DATE Modified (#409.3) (#1) SD WAIT LIST WL SPECIFIC HOSPITAL LOCATION NEW (#409.3) (#8.5) SD WAIT LIST DATE/TIME ENTERED New (#409.3) (#9.5) SD WAIT LIST ENROLLMENT PRIORITY New (#409.3) (#10.5) SD WAIT LIST CURRENT STATUS Modified (#409.3) (#23) SD WAIT LIST PATIENT CONTACT New (#409.3) (#44) SDEC APPLICATION MAJOR VERSION New (#409.81) (#.01) SDEC APPLICATION MINOR VERSION New (#409.81) (#.02) SDEC APPLICATION BUILD New (#409.81) (#.03) SDEC ACCESS BLOCK RESOURCE New (#409.821) (#.01) SDEC ACCESS BLOCK STARTTIME New (#409.821) (#.02) SDEC ACCESS BLOCK ENDTIME New (#409.821) (#.03) SDEC ACCESS BLOCK SLOTS New (#409.821) (#.04) SDEC ACCESS BLOCK ACCESS TYPE New (#409.821) (#.05) SDEC ACCESS BLOCK NOTE New (#409.821) (#1) SDEC ACCESS GROUP ACCESS GROUP New (#409.822) (#.01) SDEC ACCESS TYPE ACCESS TYPE NAME New (#409.823) (#.01) SDEC ACCESS TYPE INACTIVE New (#409.823) (#.02) SDEC ACCESS TYPE DEPARTMENT NAME New (#409.823) (#.03) SDEC ACCESS TYPE DISPLAY COLOR New (#409.823) (#.04) SDEC ACCESS TYPE RED New (#409.823) (#.05) SDEC ACCESS TYPE GREEN New (#409.823) (#.06) SDEC ACCESS TYPE BLUE New (#409.823) (#.07) SDEC ACCESS TYPE PREVENT ACCESS New (#409.823) (#.08) SDEC ACCESS GROUP TYPE ACCESS GROUP New (#409.824) (#.01) SDEC ACCESS GROUP TYPE ACCESS TYPE New (#409.824) (#.02) SDEC RESOURCE RESOURCE New (#409.831) (#.01) SDEC RESOURCE RESOURCE TYPE New (#409.831) (#.012) SDEC RESOURCE DATE/TIME ENTERED New (#409.831) (#.015) SDEC RESOURCE ENTERED BY USER New (#409.831) (#.016) SDEC RESOURCE INACTIVE New (#409.831) (#.02) SDEC RESOURCE INACTIVATED DATE/TIME New (#409.831) (#.021) SDEC RESOURCE INACTIVATED BY USER New (#409.831) (#.022) SDEC RESOURCE REACTIVATED DATE/TIME New (#409.831) (#.025) SDEC RESOURCE REACTIVATED BY USER New (#409.831) (#.026) SDEC RESOURCE TIME SCALE New (#409.831) (#.03) SDEC RESOURCE HOSPITAL LOCATION New (#409.831) (#.04) SDEC RESOURCE LETTER TEXT New (#409.831) (#1) SDEC RESOURCE NO SHOW LETTER New (#409.831) (#1201) SDEC RESOURCE CLINIC CANCELLATION LETTER New (#409.831) (#1301) SDEC RESOURCE ASSOCIATED VISTA CLINICS New (#409.831) (#2001) SDEC RESOURCE GROUP NAME New (#409.832) (#.01) SDEC RESOURCE GROUP INACTIVATION DATE New (#409.832) (#.02) SDEC RESOURCE GROUP RESOURCE New (#409.832) (#1) SDEC RESOURCE USER RESOURCENAME New (#409.832) (#.01) SDEC RESOURCE USER USERNAME New (#409.833) (#.02) SDEC RESOURCE USER OVERBOOK New (#409.833) (#.03) SDEC RESOURCE USER MODIFY SCHEDULE New (#409.833) (#.04) SDEC RESOURCE USER MODIFY APPOINTMENTS New (#409.833) (#.05) SDEC RESOURCE USER MASTEROVERBOOK New (#409.833) (#.06) SDEC ADDITIONAL RESOURCE NAME New (#409.834) (#.01) SDEC ADDITIONAL RESOURCE INACTIVE New (#409.834) (#2) SDEC APPOINTMENT STARTTIME New (#409.84) (#.01) SDEC APPOINTMENT ENDTIME New (#409.84) (#.02) SDEC APPOINTMENT CHECKIN New (#409.84) (#.03) SDEC APPOINTMENT CHECK IN TIME ENTERED New (#409.84) (#.04) SDEC APPOINTMENT PATIENT New (#409.84) (#.05) SDEC APPOINTMENT ACCESS TYPE ID New (#409.84) (#.06) SDEC APPOINTMENT RESOURCE New (#409.84) (#.07) SDEC APPOINTMENT DATA ENTRY CLERK New (#409.84) (#.08) SDEC APPOINTMENT DATE APPT MADE New (#409.84) (#.09) SDEC APPOINTMENT NOSHOW New (#409.84) (#.1) SDEC APPOINTMENT NOSHOW DATE/TIME New (#409.84) (#.101) SDEC APPOINTMENT NOSHOW BY USER New (#409.84) (#.102) SDEC APPOINTMENT REBOOK DATETIME New (#409.84) (#.11) SDEC APPOINTMENT CANCEL DATETIME New (#409.84) (#.12) SDEC APPOINTMENT CANCELLED BY USER New (#409.84) (#.121) SDEC APPOINTMENT CANCELLATION REASON New (#409.84) (#.122) SDEC APPOINTMENT WALKIN New (#409.84) (#.13) SDEC APPOINTMENT CHECKOUT New (#409.84) (#.14) SDEC APPOINTMENT V PROVIDER IEN New (#409.84) (#.15) SDEC APPOINTMENT PROVIDER New (#409.84) (#.16) SDEC APPOINTMENT STATUS New (#409.84) (#.17) SDEC APPOINTMENT LENGTH OF APPT New (#409.84) (#.18) SDEC APPOINTMENT PREV APPT STATUS New (#409.84) (#.19) SDEC APPOINTMENT DESIRED DATE OF APPOINTMENT New (#409.84) (#.2) SDEC APPOINTMENT EXTERNAL ID New (#409.84) (#.21) SDEC APPOINTMENT APPT REQUEST TYPE New (#409.84) (#.22) SDEC APPOINTMENT NOTE New (#409.84) (#1) SDEC PREFERENCES AND SPECIAL PATIENT New (#409.845) (#.01) SDEC PREFERENCES AND SPECIAL PREFERENCES New (#409.845) (#1) PREFERENCES SUB-FILE PREFERENCE New (#409.8451) (#.01) PREFERENCES SUB-FILE DATE/TIME ADDED New (#409.8451) (#2) PREFERENCES SUB-FILE ADDED BY USER New (#409.8451) (#3) PREFERENCES SUB-FILE INACTIVE DATE New (#409.8451) (#4) PREFERENCES SUB-FILE INACTIVATED BY USER New (#409.8451) (#5) PREFERENCES SUB-FILE REMARKS New (#409.8451) (#6) SDEC APPT REQUEST PATIENT New (#409.85) (#.01) SDEC APPT REQUEST CREATE DATE New (#409.85) (#1) SDEC APPT REQUEST INSTITUTION New (#409.85) (#2) SDEC APPT REQUEST REQUEST TYPE New (#409.85) (#4) SDEC APPT REQUEST REQ SPECIFIC CLINIC New (#409.85) (#8) SDEC APPT REQUEST REQ SERVICE/SPECIALTY New (#409.85) (#8.5) SDEC APPT REQUEST ORIGINATING USER New (#409.85) (#9) SDEC APPT REQUEST DATE/TIME ENTERED New (#409.85) (#9.5) SDEC APPT REQUEST PRIORITY New (#409.85) (#10) SDEC APPT REQUEST ENROLLMENT PRIORITY New (#409.85) (#10.5) SDEC APPT REQUEST REQUESTED BY New (#409.85) (#11) SDEC APPT REQUEST PROVIDER New (#409.85) (#12) SDEC APPT REQUEST SCHEDULED DATE OF APPT New (#409.85) (#13) SDEC APPT REQUEST DATE APPT. MADE New (#409.85) (#13.1) SDEC APPT REQUEST APPT CLINIC New (#409.85) (#13.2) SDEC APPT REQUEST APPT INSTITUTION New (#409.85) (#13.3) SDEC APPT REQUEST APPT STOP CODE New (#409.85) (#13.4) SDEC APPT REQUEST APPT CREDIT STOP CODE New (#409.85) (#13.5) SDEC APPT REQUEST APPT STATION NUMBER New (#409.85) (#13.6) SDEC APPT REQUEST APPT CLERK New (#409.85) (#13.7) SDEC APPT REQUEST APPT STATUS New (#409.85) (#13.8) SDEC APPT REQUEST SERVICE CONNECTED PERCENTAGE New (#409.85) (#14) SDEC APPT REQUEST SERVICE CONNECTED PRIORITY New (#409.85) (#15) SDEC APPT REQUEST DATE DISPOSITIONED New (#409.85) (#19) SDEC APPT REQUEST DISPOSITIONED BY New (#409.85) (#20) SDEC APPT REQUEST DISPOSITION New (#409.85) (#21) SDEC APPT REQUEST CID/PREFERRED DATE OF APPT New (#409.85) (#22) SDEC APPT REQUEST CURRENT STATUS New (#409.85) (#23) SDEC APPT REQUEST COMMENTS New (#409.85) (#25) SDEC APPT REQUEST MULTIPLE APPOINTMENT RTC New (#409.85) (#41) SDEC APPT REQUEST MULT APPT RTC INTERVAL New (#409.85) (#42) SDEC APPT REQUEST MULT APPT NUMBER New (#409.85) (#43) SDEC APPT REQUEST MRTC CALC PREF DATES New (#409.85) (#43.5) SDEC APPT REQUEST PATIENT CONTACT New (#409.85) (#44) 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 IDX REFRESH run routine NEW SDECRPC Broker (Client/Server) NEW Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- SDEC ADD APPOINTMENT NEW SDEC CANCEL APPOINTMENT NEW SDEC CHECKIN APPOINTMENT NEW SDEC NOSHOW APPOINTMENT NEW Security Keys Associated: Security Key Name ----------------- SDECZMENU SDECZMGR Templates Associated: Template Name Type File Name (#) New/Modified/Deleted ------------- ---- ------------------ -------------------- SDB INPUT HOSPITAL LOCATION (44) Modified SDRR RECALL CARD ADD INPUT RECALL REMINDERS (403.5) Modified Additional Information: N/A New Service Requests (NSRs): ----------------------------- N/A Patient Safety Issues (PSIs): ------------------------------ N/A Remedy Ticket(s) & Overviews: ----------------------------- N/A Test Sites: ----------- Asheville Chillicothe VAMC Hudson Valley Salt Lake City 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 -------------------------------------------------------------------------- SCHEDULING User Manual VSE_UG.PDF (binary) SCHEDULING Technical Manual VSE_TM.PDF (binary) SCHEDULING Security Guide VSE_SG.PDF (binary) SCHEDULING Install Guide VSE_Install_Guide.PDF (binary) Patch Installation in TEST ONLY ***DO NOT INSTALL INTO PRODUCTION***: Pre/Post Installation Overview ------------------------------ There is not a Pre-Installation routine. The Post-Installation routine does the following functions: 1. Registers the new RPCs to the SDECRPC option. 2. Checks the validity of existing cross-references that are used by Remote Procedures of VS GUI. No changes are made. 3. Initializes new Mumps cross-references: - "AVADPR" in the HOSPITAL LOCATION file (#44) - "AG" in the HOSPITAL LOCATION file (#44) - "AC" in the SD WAIT LIST file (#409.3) - "AD" in the SD WAIT LIST file (#409.3) - "AE" in the SD WAIT LIST file (#409.3) - "E" in the SD WAIT LIST FILE (#409.3) - "AC" in the RECALL REMINDERS file (#403.5) - "AC" in the RECALL REMINDERS REMOVED file (#403.56) 4. Populates the new SDEC RESOURCE file (#409.831) with clinics from the HOSPITAL LOCATION file (#44) as clinic resources, providers and privileged users as provider resources. 5. Adds AVAILABLE and UNAVAILABLE entries to the new SDEC ACCESS TYPE file (#409.823). 6. Populates the new SDEC APPOINTMENT file (#409.84) from existing patient appointments in the PATIENT file (#2). 7. Schedules the SDEC IDX REFRESH option in TaskMan. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Scheduling/Patches/SD_5.3_627

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 anonymous@download.vista.domain.ext from the COMMAND prompt (example: sftp anonymous@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: When using Attachmate Reflection (Secure Shell): Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext When using the COMMAND prompt (example: sftp anonymous@domain.ext): Albany: anonymous@domain.ext Hines: anonymous@domain.ext Salt Lake City: anonymous@domain.ext 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: PCR REPORT, UNIQUE CLAIM ID AND ANESTHESIA MIN Description: ============ This patch addresses the following 3 issues: 1. Items are missing from the Potential Cost Recovery (PCR) report when a patient has multiple authorizations on the same day. 2. The direct global read of the SHORT NAME (#2) field in the CPT (#81) file must be updated to the current Application Programming Interface (API) for the short name to continue to display on the Fee Basis Patch 135 Unique Claim Identifier Display report after the release of IPCT*4.0*46. 3. The ANESTHESIA MINUTES (#43) field in the FEE BASIS PAYMENT (#162) file needs to be expanded from 3 to 4 digits to properly process anesthesia for labor and delivery. ASSOCIATED REMEDY TICKETS: ========================== 1. INC000001226511 - Bug in Fee Basis Potential Cost Recovery (PCR) report 2. INC000001105362 - CPT direct global read - Fee Basis (FB) 3. INC000001111269 - Fee Basis - Other ASSOCIATED NSR(S): ================== N/A PARTICIPATING TEST SITES: ========================= Battle Creek VAMC Edward Hines Jr. VA Hospital (Hines) REMEDY OVERVIEW: ================ 1. INC000001226511 - Bug in Fee Basis Potential Cost Recovery (PCR) report Problem: -------- Items are missing from the Potential Cost Recovery (PCR) report when a patient has multiple authorizations on the same day. In cases where there are multiple authorizations in the AUTHORIZATION (#161.01) sub-file of the FEE BASIS PATIENT (#161) file for the same patient and date, the system currently only examines the first Authorization found for the patient and date. Resolution: ----------- Routine FBPCR3 was modified to loop through all authorizations in the AUTHORIZATION (#161.01) sub-file of the FEE BASIS PATIENT (#161) file for the same patient and date. 2. INC000001105362 - CPT direct global read - Fee Basis (FB) Problem: -------- After the installation of patch ICPT*6.0*46, the SHORT NAME (#2) field will be deleted and will not show on the Fee Basis Patch 135 Unique Claim Identifier Display report in option Unique Claim Identifier Display [FB UCID DISPLAY]. Resolution: ----------- Routine FBUTL135 was modified to replace two direct global reads to API calls in routine ICPTCOD. 3. INC000001111269 - Fee Basis - Other Problem: -------- The Business has identified an inability to appropriately capture & price anesthesia minutes of service for Labor and Delivery (L&D) cases (in VistA Fee/FBCS) due to a maximum data field length restriction of 3 characters 0 - 999. L&D services often exceed that restricted field length. Resolution: ----------- The ANESTHESIA MINUTES (#43) field of the FEE BASIS PAYMENT (#162) file was modified to expand from 3 digits to 4 digits to properly process anesthesia for labor and delivery. ********************BEFORE*********************** DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE -------------------------------------------------------------------------- 162.03,43 ANESTHESIA TIME (MINUTES) 2;11 NUMBER INPUT TRANSFORM: K:+X'=X!(X>999)!(X<15)!(X?.E1"."1N.N) X LAST EDITED: MAY 05, 1999 HELP-PROMPT: Type a Number between 15 and 999, 0 Decimal Digits DESCRIPTION: Enter time billed for an anesthesia service in minutes. The bill may specify anesthesia units which will need to be converted to minutes. ********************AFTER*********************** DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE -------------------------------------------------------------------------- 162.03,43 ANESTHESIA TIME (MINUTES) 2;11 NUMBER INPUT TRANSFORM: K:+X'=X!(X>9999)!(X<15)!(X?.E1"."1N.N) X LAST EDITED: AUG 04, 2015 HELP-PROMPT: Type a Number between 15 and 9999, 0 Decimal Digits DESCRIPTION: Enter time billed for an anesthesia service in minutes. The bill may specify anesthesia units which will need to be converted to minutes. 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_166

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

Navigation Menu

Uh oh!

Update ZISHGUX.m - #2

Update ZISHGUX.m#2
ksbhaskar wants to merge 1 commit into
WorldVistA:masterfrom
ksbhaskar:patch-2

ksbhaskar commented Jan 29, 2015

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

ksbhaskar commented Jan 29, 2015

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant