Update per VistA convergence conference calls Nov/Dec 2013 #1

ksbhaskar · 2013-12-14T18:13:26Z

No description provided.

ChristopherEdwards · 2013-12-16T12:33:50Z

Bhaskar:

Thanks for the patch. I'll add this to the Code Convergence issue tracker (http://issues.osehra.org/browse/VISTA-85).

As a heads up this pull request probably won't be merged here but included in the code convergence patch (KIDS build) for Kernel when we are ready.

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: ALFUZOSIN TRADE NAME ALLERGY CLASS UPDATE Description: ============ Patch PSN*4.0*471 addresses the following issue: Alfuzosin patient allergies with a Trade Name in the REACTANT field (#.02) need to be updated to remove VA Drug Class HORMONES/SYNTHETICS/MODIFIERS,OTHER (HS900) Associated NSR(s): ================== N/A Associated Trouble Ticket(s): ============================= I7357301FY16 - Old VA Drug class needs to be removed from ALFUZOSIN patient allergies where the Reactant is a Trade Name Participating Test Sites: ========================= Oklahoma City VAMC Chillicothe VAMC Central Plains HCS Ticket Overview: ================ I7357301FY16 - Old VA Drug class needs to be removed from ALFUZOSIN patient allergies where the Reactant is a Trade Name Problem: -------- Old VA Drug Class HORMONES/SYNTHETICS/MODIFIERS,OTHER (HS900) in Trade Name based ALFUZOSIN patient allergies is causing invalid allergy order checks. Solution: --------- This patch updates records in the PATIENT ALLERGIES file (#120.8) where the GMR ALLERGY field (WorldVistA#1) contains Alfuzosin VA Generic and where the REACTANT field (#.02) contains a Trade Name for one of the corresponding VA Products. Class HS900 is removed from these patient allergies (from the VA DRUG CLASS field (#.01) in sub file (#120.803)). Allergies entered in error and allergies for deceased patients will not be updated. Note some sites might not have any Trade Name patient allergies that need to be updated. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/b0ced814/Packages/National+Drug+File/Patches/PSN_4.0_471

Patch Subject: MEDICAL CARE COLLECTION FUND (MCCF) ENHANCEMENTS PROJECT - EPAYMENTS Description: ============ ************************************************************************* NOTICE: The patch bundle PRCA IB MCCF EDI 1.0 (IB*2.0*530/PRCA*4.5*303) must be installed first, then install two standalone patches, IB*2.0*529 and PRCA*4.5*304. Patch IB*2.0*529 must be installed before installing PRCA*4.5*304. Install all patches close together so that your site has all of the features released as part of this enhancement. ************************************************************************* The Medical ePayments Compliance (Phase 2, Iteration 2) project ensures the Veterans Administrations (VA) compliance with Electronic Funds Transfer (EFT) & Electronic Remittance Advice (ERA) Operating Rules, and enables VA to more effectively use ERA data, resulting in better revenue and cash flow management. It will provide the infrastructure foundation for electronic exchange of claim payment information and promotes an interoperable system and will reduce the time elapsed between receipt of the Electronic Data Interchange (EDI) 835 Electronic Remittance Advice Transaction and receipt of the Cash Concentration or Disbursement (CCD+) transactions. It will ensure that trace numbers between payments and remittances can be used by VA, reducing the level of open accounts receivable, allow claim denials to be more quickly addressed, and standardizes Electronic Funds Transfer (EFT) & ERA enrollment to reduce workload burden on VA staff. This patch contains changes to the ePayments (835 and EFT) program area to ensure compliance. Specifically, enhancements to the Veterans Health Information Systems and Technology Architecture (VistA) Third Party EDI Lockbox module to increase timely and accurate processing of payments for electronic pharmacy claims in compliance with Health Insurance Portability and Accountability Act (HIPAA) and Veterans Health Administration (VHA) Fiscal Accounting policies will also be required. The ePayments system is used by Accounts Receivable (AR) staff to process payments from third party payers for both medical and pharmacy claims. The objectives of the requested ePayments software modifications are to expedite accurate payments by enhancing the ePayments software to streamline the user's ability to process the pharmacy 835 while: Complying with HIPAA legislative requirements to meet patient needs and secure Protected Health Information (PHI). Conducting payment accounting in accordance with the Office of Management and Budget (OMB) directives. Systematically enforcing VHA Fiscal Accounting policy. This patch adds the following: - Modifies the Insurance Payment Trend Report to accurately identify Insurance Companies listed on the report by including their Tax Identification Number. - Modifies the Insurance Payment Trend Report to identify whether a patient's claim has an ERA attached to it. - Adds an Index to the EDI TRANSMISSION BATCH file to allow for easier searches Patch Components: ----------------- Files & Fields Associated: File Name (#) New/Modified/ Sub-File Name (#) Field Name (#) Deleted ------------- ------------------------------ ------------- EDI TRANSMISSION DATE FIRST SENT (WorldVistA#1.01) Modified BATCH (#364.1) 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 List Templates: List Template Name New/Modified/Deleted ------------------ -------------------- N/A Templates Associated: Template Name Type File Name (#) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: N/A New Service Requests (NSRs): ----------------------------- 20130518 - Medical ePayments Compliance (Phase 2, Iteration 2) Patient Safety Issues (PSIs): ------------------------------ N/A Remedy Ticket(s) & Overviews: ----------------------------- N/A Test Sites: ----------- Alexandria VA Health Care System (Alexandria, LA)-Station 502 Huntington VA Medical Center (Huntington, WV)-Station 581 South Texas Veterans Health Care System (San Antonio, TX)-Station 671 Software and Documentation Retrieval Instructions: ---------------------------------------------------- Software being released as a host file and/or 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 Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ File Description File Name FTP Mode ---------------------------------------------------------------------- INTEGRATED BILLING User Manual IB_2_0_UM.PDF (binary) INTEGRATED BILLING Technical Manual/ IB_2_0_TM.PDF (binary) Security Guide INTEGRATED BILLING Release Notes IB_2_0_P529_RN.PDF (binary) EPAYMENTS USER MANUAL (EDI LOCKBOX) EPAYMENTS_USER_ (binary) MANUAL_R0516.PDF Patch Installation: Pre/Post Installation Overview ------------------------------ Note: The patch bundle PRCA IB MCCF EDI 1.0 (IB*2.0*530/PRCA*4.5*303) must be installed first, then install two standalone patches, IB*2.0*529 and PRCA*4.5*304. Patch IB*2.0*529 must be installed before installing PRCA*4.5*304. Install all patches close together so that your site has all of the features released as part of this enhancement. Post Install routine will reindex the modified files for the new index. You may delete the post install routine IB20P529 after installation. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/b0ced814/Packages/Integrated+Billing/Patches/IB_2.0_529

Patch Subject: MEDICAL CARE COLLECTION FUND (MCCF) ENHANCEMENTS PROJECT - EPAYMENTS Description: ============ ************************************************************************* NOTICE: The patch bundle PRCA IB MCCF EDI 1.0 (IB*2.0*530/PRCA*4.5*303) must be installed first, then install two standalone patches, IB*2.0*529 and PRCA*4.5*304. Patch IB*2.0*529 must be installed before installing PRCA*4.5*304. Install all patches close together so that your site has all of the features released as part of this enhancement. ************************************************************************* The Medical ePayments Compliance (Phase 2, Iteration 2) project ensures the Veterans Administrations (VA) compliance with Electronic Funds Transfer (EFT) & Electronic Remittance Advice (ERA) Operating Rules, and enables VA to more effectively use ERA data, resulting in better revenue and cash flow management. It will provide the infrastructure foundation for electronic exchange of claim payment information and promotes an interoperable system and will reduce the time elapsed between receipt of the Electronic Data Interchange (EDI) 835 Electronic Remittance Advice Transaction and receipt of the Cash Concentration or Disbursement (CCD+) transactions. It will ensure that trace numbers between payments and remittances can be used by VA, reducing the level of open accounts receivable, allow claim denials to be more quickly addressed, and standardizes Electronic Funds Transfer (EFT) & ERA enrollment to reduce workload burden on VA staff. This patch contains changes to the ePayments (835 and EFT) program area to ensure compliance. Specifically, enhancements to the Veterans Health Information Systems and Technology Architecture (VistA) Third Party EDI Lockbox module to increase timely and accurate processing of payments for electronic pharmacy claims in compliance with Health Insurance Portability and Accountability Act (HIPAA) and Veterans Health Administration (VHA) Fiscal Accounting policies will also be required. The ePayments system is used by Accounts Receivable (AR) staff to process payments from third party payers for both medical and pharmacy claims. The objectives of the requested ePayments software modifications are to expedite accurate payments by enhancing the ePayments software to streamline the user's ability to process the pharmacy 835 while: Complying with HIPAA legislative requirements to meet patient needs and secure Protected Health Information (PHI). Conducting payment accounting in accordance with the Office of Management and Budget (OMB) directives. Systematically enforcing VHA Fiscal Accounting policy. This patch implements the following: - Auto-posting of Pharmacy ERA payments - Auditing of Suspense item processing - Allowing ERAs with data exceptions Auto-post after corrections - Allows re-use of Deposit Ticket #'s for manually created deposit tickets - Allows the Medical Auto-decrease functionality to specify maximum decrease amounts by Claims Adjustment Reason Codes (CARC) - Add Medical and Pharmacy filters to several reports Patch Components ================ Files & Fields Associated: File Name (#) Field Name (#) New/Modified/Deleted ------------- ----------------------------------- -------------------- AR SITE PARAMETER (#342) MAX DAYS ENTRY SUSPENDED (#7.04) New AUTO POST MEDICAL PAPER BILLS (#7.05) New AUTO POST PHARMACY PAPER BILLS (#7.06) New AR BATCH PAYMENT (#344) RECEIPT # (#.01) Modified ELECTRONIC REMITTANCE ADVICE (#344.4) DATE POSTED TO SUSPENSE Modified ELECTRONIC REMITTANCE ADVICE - ERA DETAIL SUB-FILE (#344.41) CLAIM COMMENT New CLAIM COMMENT DATE New CLAIM COMMENT USER New RCDPE AUTO-PAY EXCLUSION (#344.6) EXCLUDE RX CLAIM POSTING (#.08) New PHARMACY AUTO-POST COMMENT (#3) New RCDPE PARAMETER (#344.61) AUTO-POST RX CLAIMS ENABLED (WorldVistA#1.01) New AUTO-DECREASE RX ENABLED (WorldVistA#1.02) New RCDPE CARC-RARC AUTO DEC (#344.62) New RCDPE SUSPENSE AUDIT (#344.71) New RCDPE AUTO-POST AUDIT (#344.72) New RCDPE DM REPORT PARAMETERS (#344.9) New RCDPE DM REPORT ARCHIVE (#344.91) New Forms Associated: New/Modified/ Form Name File Name (Number) Deleted --------- ------------------ ------------- N/A Mail Groups Associated: New/Modified/ Mail Group Name Deleted --------------- ------------- N/A Options Associated: New/Modified/ Option Name Type Deleted ----------- ---- ------------- Finance AR Manager Menu [PRCA menu Modified MANAGER MENU] Agent Cashier Menu [RCDP AGENT menu Modified CASHIER MENU] EDI Lockbox (ePayments) menu Modified Reports Menu [RCDPE EDI LOCKBOX REPORTS MENU] EDI Diagnostic Measures menu New Reports [RCDPE EDI NATIONAL REPORTS] EDI VOLUME STATISTICS Report run routine New [RCDPE EDI VOLUME STATISTICS] EFT/ERA TRENDING Report run routine New [RCDPE EFT-ERA TRENDING REPORT] ERA Status Change Audit Report run routine New [RCDPE ERA STATUS CHNG AUD REP] Disable-Enable DM Background run routine New Job/Reports [RCDPE NR DISABLE/ENABLE] EDI Diagnostic Measures menu New Extracts Menu [RCDPE NR EXTRACT MENU] Manually Start DM Extract run routine New [RCDPE NR MANUAL START] Manually Transmit DM Extract run routine New [RCDPE NR MANUAL TRANSMIT] View/Print Extracted Reports run routine New [RCDPE NR VIEW/PRINT EXTRACTS] Link Payment Tracking Report run routine New [RCDPE SUSPENSE AUDIT REPORT] Parameter Definitions: New/Modified/ Parameter Name Deleted -------------- ------------- RCDPE APAR Modified Protocols Associated: New/Modified/ Protocol Name Deleted ------------- ------------- RCDP LINK PAYMENTS SUSPENSE REPORT Modified RCDPE APAR CLAIM COMMENT New RCDPE APAR EEOB REFRESH Modified RCDPE APAR EEOB REVIEW Modified RCDPE APAR RESEARCH Modified RCDPE APAR SELECTED EEOB MENU Modified RCDPE APAR SPLIT LINE Modified RCDPE APAR VERIFY Modified RCDPE APAR VIEW/PRINT EOB Modified RCDPE APAR VIEW/PRINT ERA Modified RCDPE EOB WL RECEIPT VIEW Modified RCDPE EOB WL REVIEW Modified RCDPE EOB WORKLIST CHANGE VIEW Modified RCDPE EOB WORKLIST DIST ADJ Modified RCDPE EOB WORKLIST MARK FOR AUTO POST New RCDPE EOB WORKLIST MENU Modified RCDPE EOB WORKLIST RECEIPT PROCESSING Modified RCDPE EOB WORKLIST REFRESH Modified RCDPE EOB WORKLIST SPLIT LINE Modified RCDPE EOB WORKLIST VERIFY Modified RCDPE MARK FOR AUTOPOST New RCDPE VIEW/PRINT WORKLIST ERA Modified RCDPE WORKLIST ERA LIST MENU Modified RCDPE WORKLIST ERA MARK FOR AUTO POST New Security Keys Associated: New/Modified/ Security Key Name Deleted ----------------- ------------- N/A List Templates: New/Modified/ Template Name Type Deleted ------------- ---- ------------- RCDP DEPOSIT PROFILE List Modified RCDP LINK PAYMENTS TO ACCOUNTS List Modified RCDPE WORKLIST ERA LIST List Modified Templates Associated: New/Modified/ Template Name Type File Name (Number) Deleted ------------- ---- ------------------ ------------- RCMS EDI LOCKBOX Input AR SITE PARAMETER (#342) Modified Additional Information: ----------------------- N/A New Service Requests (NSRs): ----------------------------- 20130518 - Medical ePayments Compliance (Phase 2, Iteration 2) Patient Safety Issues (PSIs): ------------------------------ N/A Remedy Ticket(s) & Overviews: ----------------------------- 1. INC1269592/INC1282993: EFTs posted to paper EOBs are not showing up on reports and causing stale dated lockups. Problem: -------- When processing EFTs with paper EOBs, EFTs are not marked as posted in VistA. Consequently, they are still showing up on reports and causing stale dated lockups. Resolution: ----------- After investigating, this was determined to be a training issue as users at some sites were not properly closing receipts after the EFT was posted to a paper EOB. No programming changes were needed. 2. INC1289740: Auto-Posting of ERA line items does not always work. Problem: -------- During auto-posting of (ERA) line items that were marked for auto-posting, if the payment amount was greater than the claim balance, processing of ERA line items stopped and the remainder of the line items did not process. In addition, the line items did not go back on the Auto-Post Awaiting Resolution (APAR) worklist. Resolution: ----------- Any ERA line items with a payment amount less than the claim balance will post. Any line items that cannot be posted due the payment amount being greater than the claim balance will be sent to the APAR worklist. 3. INC1289572/IR277545: Receipt processing issues Problem: -------- This was actually two separate problems related to receipts: 3a. When an ERA has more than one receipt number, the APAR Header displays the incorrect receipt numbers. 3b. When a user utilizes the Split/Edit action from the APAR worklist to put dollars into Suspense and enters a comment, the comment is not displayed on the Receipt Profile or the 215 Report. Resolution: ----------- 3a. The APAR header was fixed to display the correct receipt numbers when there are multiple receipt numbers on an ERA. 3b. There was conditional logic that was used when transferring comments to the ERA detail lines. This conditional logic was removed and all comments are now transferred Subsequently, the comments will be displayed on the Receipt Profile and the 215 Report. 4. INC1289748: The Auto-Post report does not correctly display split payments. Problem: -------- The Auto-Post report does not correctly display split payments, including suspense payments. In addition, the receipt number does not always display correctly. Resolution: ----------- The Auto-Post report now displays all payments, including split payments and suspense payments. The receipt number is now correctly displayed. Test Sites: ----------- Alexandria VA Health Care System (Alexandria, LA)-Station 502 Huntington VA Medical Center (Huntington, WV)-Station 581 South Texas Veterans Health Care System (San Antonio, TX)-Station 671 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/ File Description File Name FTP Mode -------------------------------------------------------------------- ACCOUNTS RECEIVABLES Technical Manual/ PRCA_4_5_TM_R0516.PDF (binary) Security Manual ACCOUNTS RECEIVABLES Release Notes/ PRCA_4_5_P304_RN.PDF (binary) Installation Guide EPAYMENTS USER MANUAL (EDI LOCKBOX) EPAYMENTS_USER_ (binary) MANUAL_R0516.PDF Patch Installation: Pre/Post Installation Overview ------------------------------ Note: The patch bundle PRCA IB MCCF EDI 1.0 (IB*2.0*530/PRCA*4.5*303) must be installed first, then install two standalone patches, IB*2.0*529 and PRCA*4.5*304. Patch IB*2.0*529 must be installed before installing PRCA*4.5*304. Install all patches close together so that your site has all of the features released as part of this enhancement There is a post installation routine which will initially prevent your site from auto-auditing medical and pharmacy bills, and auto-posting and auto-decreasing pharmacy ERAs. After the post-install is complete you can safely remove the routine RC45P304. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/b0ced814/Packages/Accounts+Receivable/Patches/PRCA_4.5_304

Patch Subject: FY17 CHANGES FOR 4 CHAR CDS NATIONAL CLINIC (#728.441) FILE Description: ============ Patch ECX*3.0*163 updates the SHORT DESCRIPTION (WorldVistA#1) field of 3 existing entries in the NATIONAL CLINIC (#728.441) file. ASSOCIATED NSR: =============== N/A ASSOCIATED CA SDM TICKET: ========================= 1. I7805291FY16 - FY17 Changes for National Clinic entries PARTICIPATING TEST SITES: ========================= Dublin VAMC New York Harbor HCS Providence VAMC CA SDM OVERVIEW: ================ 1. I7805291FY16 Problem: -------- A request was made by the Managerial Cost Accounting Office (MCAO) to update the SHORT DESCRIPTION (WorldVistA#1) field of 3 existing entries in the NATIONAL CLINIC (#728.441) file. Resolution: ----------- Routine ECX3P163 has been created to update the NATIONAL CLINIC (#728.441) file by modifying the SHORT DESCRIPTION (WorldVistA#1) field of 3 existing entries effective 10/1/2016. The descriptions of the following entries have changed: Code New Short Description ---- --------------------- DMHC PRRC Day Hospital DMTC PRRC Day Treatment PDSC PTSD Clinical Team Program Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/b0ced814/Packages/DSS+Extracts/Patches/ECX_3.0_163

Patch Subject: ABSTRACT AND EXTRACT FIXES AND UPDATES Description: ============ This patch contains enhancements that extend and improve the functionality of the VistA OncoTrax package. The purpose of this release is to update the functionality as described below. All Data Dictionary modifications and additions have been reviewed and approved by the Data Base Administrator. CA SERVICE DESK MANAGER INCIDENTS ADDRESSED: I7282506FY16 BMC REMEDY INCIDENT ADDRESSED: INC000001107492 - IPv6 Transition for Oncology 1. Remove Recurrence Date-1st Flag if Date of First Recurrence is modified Registrars need the RECURRENCE TYPE-1ST FLAG (#165.5, #999.21) field to be deleted if the registrar modifies the DATE OF FIRST RECURRENCE (#165.5, #70) field. The RECURRENCE TYPE-1ST FLAG was added to the EDITS Modifications module in a previous patch so that users are allowed to override the calculated value. However this field needs to be reset if the recurrence is edited. This was accomplished by adding a trigger cross-reference to the DATE OF FIRST RECURRENCE (#165.5,#70) field so that if the field is modified it will delete the value in the RECURRENCE TYPE-1ST FLAG (#165.5, #999.21) field. 2. Add time stamp to the Date Case Completed and Date Case Last Changed fields To assist managers/supervisor in verification of the date and time a case was either completed or changed, the DATE CASE COMPLETED (#165.5, #90) and DATE CASE LAST CHANGED (#165.5, #198) fields will now store and display the date & time. Previously these fields only stored the date and not a time stamp, so this patch will add the time stamp to both fields. This will be displayed in the Abstract Edit Primary [ONCO ABSTRACT-EDIT] option. 3. Change Case Administration and Timeliness Report to Display Elapsed Days To Completion Two options have been updated to display the ELAPSED DAYS TO COMPLETION (#165.5, #157) field: the Timeliness Report [ONC TIMELINESS REPORT] option and the Abstract Edit Primary [ONCO ABSTRACT-EDIT] option, under the Case Administration section. This replaces the display of ELAPSED MONTHS TO COMPLETION (#165.5, #157.1) field. The reason is that the CoC's (Commission on Cancer) Completeness Report now uses days to completion rather than months to completion. 4. Add the name of the registrar who created a follow-up in the Case Administration display In the Abstract Edit Primary [ONCO ABSTRACT-EDIT] option, under the Case Administration section, the name of the registrar who last edited the Abstract, stored in the CASE LAST CHANGED BY (#165.5, #199) field is displayed after the DATE CASE LAST CHANGED (#165.5, #198) field. This field will be triggered to record the name of the registrar who did the editing even if it was a Follow-Up added. 5. Allow registrar to over-ride '988' value stuffed in discontinued Site Specific Factor (SSF) fields For SSF fields that have been discontinued a value of '988' is stuffed into the fields. It was not possible for registrars to go in and enter a value for those fields. Some sites however, may still choose to use those fields even though they have been discontinued by Collaborative Staging. For this reason, this patch will add checks to the stuffing of discontinued fields to check if the SSF has a value first and if so do not stuff; this allows the registrar to enter a value which will override the stuffed value. 6. Expand the Performance Status at DX codes Expand the allowable selections for the PERFORMANCE STATUS AT DX (#165.5, #227) field to include ECOG and KPS (Karnofsky Performance Scale) values. No conversion of existing data is necessary. The description and help text for this field has also been expanded and modified for the new selections. The newly added codes are: 0 ECOG 0 1 ECOG 1 2 ECOG 2 3 ECOG 3 4 ECOG 4 5 ECOG 5 9 UNKNOWN 10 KPS 10 20 KPS 20 30 KPS 30 40 KPS 40 50 KPS 50 60 KPS 60 70 KPS 70 80 KPS 80 90 KPS 90 100 KPS 100 7. Remove Clinical and Pathologic TNM fields from required items To change an Abstract Status to "Complete" there is a list of required data items that must be filled in. If any of these fields are not entered there is a warning displayed and the abstract will not change to complete. The CLINICAL T (#165.5, #37.1), CLINICAL N (#165.5, #37.2), PATHOLOGIC T (#165.5, #85) and PATHOLOGIC N (#165.5, #86) fields are no longer required to complete an abstract and have been removed from the required fields check. 8. Update the text for Surgical Procedure code selection #15 of LUNG (C34._) cases For LUNG (C34._) cases, the SURGERY OF PRIMARY (F) (#165.5, #58.6) field will be updated to add the text "; RFA" to code selection #15. The new code text will now look like this: 15 Local tumor destruction, NOS; RFA 9. Add 10 User Defined Fields (UDF) for creation and use at each facility Add 10 new fields in the abstract, UDF #1 - #10. The fields are free text, 1-6 characters long. These 10 new fields have been added to the Abstract Edit Primary [ONCO ABSTRACT-EDIT] option in a new module: 9. User-Defined Fields. They will also show up within the Abstract towards the end just before the Abstract Status. 10. Add newly required codes to Other Staging System Expand the allowable selections for the OTHER STAGING SYSTEM (#165.5, #39) field. This field is a pointer to the OTHER STAGING FOR ONCOLOGY (#164.3) File. The new PCLC and UNOS codes have been added to the file for selection in the OTHER STAGING SYSTEM field. The newly added fields are: BCLC A0 BCLC A1 BCLC A2 BCLC A3 BCLC A4 BCLC B BCLC C BCLC D UNOS T1 UNOS T2 UNOS T3 UNOS T4a UNOS T4b 11. Add new Clinical and Pathologic Stage Descriptor fields to the Abstract Add CLINICAL STAGE DESCRIPTOR (#165.5, #241) and PATHOLOGIC STAGE DESCRIPTOR (#165.5, #242) fields to the abstract (after the STAGE GROUP fields) for all primary sites. The codes and help text for these set of codes fields was also expanded. 12. Screen C18.1 cases from RQRS option regardless of selected sorting fields Screen the C18.1 (67181) cases from the Create RQRS Extract [CREATE RQRS EXTRACT] option when user runs the option sorted by DATE CASE LAST CHANGED (#165.5, #198) or ACCESSION NUMBER (#165.5, #.05). Currently the C18.1 cases are only screened when the user runs the option sorted by DATE DX (#165.5, #3). 13. Remove of the Print Abstract-Brief (80c) [PRINT ABSTRACT-BRIEF 80] option The Print Abstract-Brief (80c) [PRINT ABSTRACT-BRIEF 80] option which had been marked for deletion previously, will be removed from the Abstracting/Printing [ABSTRACT ENTRY/PRINT] menu. 14. Remove skipping of Performance Status at DX For abstracts which skip over the Staging/TNM coding (for instance, UNKNOWN primaries) the abstract would also skip past the PERFORMANCE STATUS AT DX (#165.5, #227) field. This has been modified so that the PERFORMANCE STATUS AT DX field is not skipped and may be edited by the user. 15. Correct auto-staging for angiosarcoma and malignant mesenchymoma cases For C38._ and C49._ cases with Histology of 8990/3 or 9120/3 the Abstract Edit Primary [ONCO ABSTRACT-EDIT] option would stuff the staging fields with '88' and skip over this section. This is no longer correct and will be fixed. For these cases the fields will no longer be stuffed and skipped; the registrars will now be able to edit these fields. 16. New selection in RQRS Option to select All Analytic Cases Previously the Create RQRS Extract [ONCO RQRS EXTRACT] option would only include Breast, Colon and Rectum cases. A new selection is needed which will allow the user to select ALL cases. The previous selection will remain so users can run the report either by selecting ALL cases or only Breast, Colon and Rectum cases. 17. Internet Protocol v6 Routines ONCX10 and ONCXURL will be updated to allow for handling of new Internet Protocol v6 format, while retaining the existing functionality to handle the old Internet Protocol v4 format. Since the IPv6 is not yet in use, installation and testing of this functionality should just confirm that no new problems are introduced and that Collaborative Staging and EDITS continue to work correctly. 18. Correct EDITS error returned for C17.9 cases with Histology of 9930/3 When completing an abstract for cases with PRIMARY SITE (#165.5, #20) field = "C17.9" and HISTOLOGY (ICD-O-3) (#165.5, 22.3) field = "99303" an EDITS error was being returned. The EDITS error indicated a "00" for SURGERY OF PRIMARY (F) (#165.5, #58.6) field. The OncoTrax code was sending an incorrect value for field #58.6 to the EDITS URL which was resulting in an error being returned by the EDITS. This code was modified to send the correct value for field #58.6 which eliminates the EDITS error. 19. Accession Only Abstract Status trigger Abstracted By field When setting an ABSTRACT STATUS (#165.5, #91) to "Accession Only" a trigger will be added to set the ABSTRACTED BY (#165.5, #92) field to record the Registrar's Name. Previously this field was only triggered for Abstracts to "Complete". This is needed for QA at sites so that facilities will be able to track "Accession Only" cases. 20. Update code text value for SEER Summary Stage For the SEER SUMMARY STAGE 2000 (#165.5, #35) and SEER SUMMARY STAGE ABBREVIATED (#165.5, #35.1) fields the text value for selection #8 needs to be updated to "NA/Benign". 21. Exclude ICD10 PHI Codes from ACOS & State/VACCR Data Download options The Create ACOS Data Download [ONCO #SITE-CREATE ACOS DISK] and Create State/VACCR Data Download [ONCO #STATE DATA DISK] options were excluding ICD9 PHI codes from the COMORBIDITY section if the user chose to exclude them. This patch will also allow the user to exclude the ICD10 PHI codes from the SECONDARY DIAGNOSIS section if the user chooses to exclude them. 22. Value of N88 not allowed for CLIN & PATH T,N,M,GROUP fields for C44 cases For Cutaneous Leiomyosarcoma cases with Primary Site = C44 and Histology = 8890/3 the user was not able to enter the '88' value for Clinical and Pathologic Staging fields. This is fixed so that '88' values are allowed and show up in the help text. 23. Histology 9421/1 obsolete for cases with DATE DX of 1/1/2001 or later For cases with a Date DX of 1/1/2001 or later the Histology of 9421/1 is obsolete and will no longer be selectable. The user will see the following message: 94211 is obsolete for primaries starting 2001!!!! 24. Update of the Health Summary ONC Remote Data View The Collaborative Staging section will be removed from the Health Summary ONC Remote Data View. This was required due to the display of old/outdated AJCC 6th Edition fields. Also, since Collaborative Staging of TNM values will be retired with 2016 and later cases, these obsolete fields should be removed from the displays anyway. These changes are included in the associated Health Summary patch, GMTS*2.7*117, which must be installed in conjunction with patch ONC*2.2*5. 25. CA Service Desk Incident # 7282506FY16: Queuing Issue in Automatic Casefinding-PTF Search Option The Automatic Casefinding-PTF Search [ONCO SUSPENSE-CASEFIND (PTF)] option was modified for ICD-10 in Patch ONC*2.2*7, but a problem with queueing the report was found. If the report was queued to print at a later time, the report would error out with an Undefined SBCIND variable. This has been fixed. 26. New HEMA @fac Fields Created and Added to the Abstract Two new @fac fields were created and added to the Abstract: HEMA TRANS/ENDOCRINE PROC @fac (#165.5, #153.2) and HEMA TRANS/ENDOCRINE PR@FAC DT (#165.5, #153.3). These 2 new fields have been added to the Abstract Edit Primary [ONCO ABSTRACT-EDIT] option for display and editing. The 2 fields were also added to the Print Abstract-Extended (80c) [ONCO ABSTRACT-EXTENDED 80] and Print Complete Abstract (132c) [ONCO ABSTRACT-PRINT/E0132] report options. 27. Change Default of Secondary Diagnosis Prompt to YES In the Complete Abstract [ONCOXM10] option the default value for the "Would you like to edit the SECONDARY DIAGNOSIS #1-10 prompts" has been changed from "No" to "Yes". 28. Fix Code for Follow-Up Status (#160, #15.2) Field & Convert Incorrect Values The FOLLOW-UP STATUS (#160, #15.2) field was not being set correctly by the OncoTrax software. This field is not editable by the Registrars, it is only set within the code. For patients with only 1 Primary and a Class of Case for that primary of 00 or 30-99 the Follow-Up Status should always be set to 0 (Inactive). The code was allowing these to be set to 1 (Active) or 8 (LTF) which was not correct. The code to set the field was corrected and an item was added to the Post-Init routine to correct any bad values in existing entries. 29. Correct Staging for Waldenstrom Cases (Primary Site=C42.0, Histology=9761/3) Waldentrom Cases with SITE/GP=HEMATO/RETICULO, PRIMARY SITE=C42.0 and HISTOLOGY=9761/3 were not staging correctly. These cases were not correctly dropping into the 'SYSTEMIC DISEASE - No EOD/TMN Coding' section. This is now corrected so that these cases will drop into the correct staging and have the correct default values filled in. 30. Correct the TNM Staging for Pancreas Cases with Histology = 8240 - 8244 Pancreas Cases with a Histology in the range of 8240-8244 were defaulting the TNM Staging values to 88's. Previously this was correct because these cases were excluded from TNM Staging, but beginning in 2010 these Histologies are now included as part of the Pancreas schema. This is corrected so that these cases will allow TNM staging values to be entered. Patch Components ================ Routines: --------- This release contains 34 routines. Files & Fields Associated: File Name (#) Field Name (#) New/Modified/Deleted ------------- ------------------ -------------------- ONCOLOGY PRIMARY (#165.5) SEER SUMMARY STAGE 2000 (#35) Modified RADIATION @fac (#51.4) Modified CHEMOTHERAPY @fac (#53.3) Modified HORMONE THERAPY @fac (#54.3) Modified IMMUNOTHERAPY @fac (#55.3) Modified OTHER TREATMENT @fac (#57.3) Modified DATE OF FIRST RECURRENCE (#70) Modified DATE CASE COMPLETED (#90) Modified DATE CASE LAST CHANGED (#198) Modified PERFORMANCE STATUS AT DX (#227) Modified HEMA TRANS/ENDOCRINE PROC @fac (#153.2) New HEMA TRANS/ENDOCRINE PR@FAC DT (#153.3) New TNM CLIN DESCRIPTOR (#241) Modified TNM PATH DESCRIPTOR (#242) Modified UDF1 (#284) New UDF2 (#284.1) New UDF3 (#284.2) New UDF4 (#284.3) New UDF5 (#284.4) New UDF6 (#284.5) New UDF7 (#284.6) New UDF8 (#284.7) New UDF9 (#284.8) New UDF10 (#284.9) 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 (#) New/Modified/Deleted ------------- ---- ------------- -------------------- ONCO ABSTRACT-I Input #165.5 Modified ONCOY55 Print #165.5 Modified Test Sites ========== Hines VAMC Washington, DC VAMC West Haven, Ct Documentation Retrieval: ======================== There is no new documentation associated with this patch. Patch Installation: Pre/Post Installation Overview ============================== There is no pre-installation routine, but there is a post installation routine (ONC2PS05) associated with this patch. The routine ONC2PS05 may optionally be deleted by the installer after the installation is complete. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Oncology/Patches/ONC_2.2_5

Patch Subject: STATE PRESCRIPTION MONITORING PROGRAM (SPMP) ENHANCEMENT Description: ============ The State Prescription Monitoring Program (SPMP) Enhancement project was established to further enhance the VistA SPMP functionality released by patch PSO*7*408 in September 2014. The SPMP VistA functionality is used to identify prescriptions for controlled substance drugs, Schedule 2 through 5, dispensed to veterans by the Veterans Health Administration (VHA) Outpatient Pharmacy facilities and to create and transmit an export file containing this information to the Prescription Drug Monitoring Program (PDMP) of each state on a daily basis. During the implementation of PSO*7*408, it was discovered that some states had unique requirements that could not be addressed by current functionality. As a result transmissions to those states were rejected. Patch PSO*7*451 will enhance the SPMP functionality to allow VHA to fulfill specific state requirements and successfully transmit data to those states PDMPs. This patch also enhances the management of Secure SHell (SSH) Keys by streamlining the creation of SSH Keys and restricting user access to the Private SSH Key content. In addition, a few miscellaneous issues have also been addressed, which are described below. All the changes introduced by this patch were related to the options under the State Prescription Monitoring Program (SPMP) Menu [PSO SPMP MENU] which is located under the Supervisor Functions [PSO SUPERVISOR] menu option. The following functionality enhancements will be delivered by this patch: 1. View/Edit ASAP Definitions [PSO SPMP ASAP DEFINITIONS] option ------------------------------------------------------------- Some extensive enhancements have been made to this option to allow full user customization of the American Society for Automation in Pharmacy (ASAP) data definition format (protocol) used to report outpatient controlled substance prescription data to the states. a) The term '/Edit' has been added to the external name of this option and the term 'VIEW' was removed from the internal option name. b) This option has been modified to include full customization capability for the ASAP definitions 3.0 and later versions, which will allow sites to fulfill states PDMPs' specific requirements. Moreover, sites will be able to create new ASAP versions by copying an existing one, which will hopefully allow them to continue transmissions well into the future as new ASAP versions are released and adopted by the state's PDMPs. Below is a list of actions that have been added to this option: CV Copy ASAP Version CE Customize Element ED Edit Delimiters CS Customize Segment DC Delete Customization For more information on these new actions see the Outpatient Pharmacy Manager's User Manual in the State Prescription Monitoring Program (SPMP) section. c) Customized Data Elements and Segments will be identified by an '*' (asterisk) displayed to the right of the Data Element or Segment ID. 2. View/Edit SPMP State Parameters [PSO SPMP STATE PARAMETERS] option ------------------------------------------------------------------ A few modifications have been made to this option to support the new functionality released by this patch. a) The parameter WINDOWS/NT LOCAL DIRECTORY was removed from this option because this module no longer supports this operating system due to the increase in the complexity for handling SSH Keys and the fact that VHA does not use WINDOWS/NT operating system for VistA database at any of its sites. b) The parameter REPORTING FREQUENCY IN DAYS was modified to allow a maximum value of 30 days. Before this field allowed a maximum value of 99 days. c) A new parameter called RENAME FILE AFTER UPLOAD was added right after the 'FILE EXTENSION' parameter. The current transmission creates and sends the data file with the ".UP" file extension (for "upload"); once the file is transmitted a command within sFTP (Secure File Transfer Protocol) is issued to rename the file to ".DAT" (or ".TXT") file extension. This new parameter will allow the site to control whether they want to keep the existing functionality by setting this parameter to 'YES' or if they would like to create and transmit the file without renaming it by setting this parameter to 'NO'. The parameter will be initially exported with a default value of 'YES', which is consistent with the existing released functionality. d) The parameters STATE SFTP SERVER IP ADDRESS and STATE SFTP SERVER USERNAME had their maximum value lengths increased from 30 to 60 and 50 characters respectively to accommodate longer PDMP's DNS (Domain Name System) names and the usernames they assign to VHA sites. e) For security reasons the parameters SFTP PRIVATE KEY TEXT and SFTP PUBLIC KEY TEXT have been removed from this option as the SSH encryption keys content will be handled by a new option called Manage Secure SHell (SSH) Keys [PSO SPMP SSH KEY MANAGEMENT], which is described below. 3. Manage Secure SHell (SSH) Keys [PSO SPMP SSH KEY MANAGEMENT] option ------------------------------------------------------------------- This new option was created to automate the management of SSH encryption keys and to improve the security regarding their content. This new option will allow sites to view the public SSH key, create a new SSH key pair and also to delete an existing SSH key pair. In addition, this new option will provide an extensive help text on how the SSH keys are used in the transmission process, which is shown below: Select one of the following: V View Public SSH Key N Create New SSH Key Pair D Delete SSH Key Pair H Help with SSH Keys Action: V// H Help with SSH Keys Secure SHell (SSH) Encryption Keys are used to automate the data transmission to the State Prescription Monitoring Programs (SPMPs). Follow the steps below to successfully setup SPMP transmissions from VistA to the state/vendor server: Step 1: Select the 'N' (Create New SSH Key Pair) Action and follow the prompts to create a new pair of SSH keys. If you already have an existing SSH Key Pair you can skip this step. You can check whether you already have an existing SSH Key Pair through the 'V' (View Public SSH Key) Action. Encryption Type: DSA or RSA? ---------------------------- Digital Signature Algorithm (DSA) and Rivest, Shamir & Adleman (RSA) are two of the most common encryption algorithms used by the IT industry for securely sharing data. The majority of SPMP servers can handle either type; however there are vendors that accept only one specific type. You will need to contact the SPMP vendor support to determine which type to select. Step 2: Share the Public SSH Key content with the state/vendor. In order to successfully establish SPMP transmissions the state/vendor will have to install/configure the new SSH Key created in step 1 for the user id they assigned to your site. Use the 'V' (View Public SSH Key) Action to retrieve the content of the Public SSH key. The Public SSH Key should not contain line-feed characters, therefore after you copy & paste it from the terminal emulator into an email or text editor make sure it contains only one line of text (no wrapping). 4. View/Export Single Prescription [PSO SPMP SINGLE RX VIEW/EXPORT] option ----------------------------------------------------------------------- This option was modified to highlight custom Data Elements and Segments by changing the font appearance according to the terminal emulator settings for highlighted text as well as by adding an '*' (asterisk) to the right of the Data Element or Segment ID. 5. View/Export Batch [PSO SPMP BATCH VIEW/EXPORT] and Export Batch Processing [PSO SPMP BATCH PROCESSING] options -------------------------------------------------------------------------- When exporting a batch through one of these two options the users will now have three different choices to execute the transmission: 'B' for Background (via TaskMan), which queues the transmission to be performed in the background through TaskMan; 'F' for Foreground, which executes the transmission in the foreground as it did before this patch and 'D' for Debug Mode (Foreground), which will execute the transmission in the foreground however it will display the sFTP debug steps, which can be very helpful for troubleshooting transmission problems. Before this patch the transmission was always executed in the foreground which made it difficult to troubleshoot issues with the transmissions, especially the scheduled transmissions, which are always executed in the background. Below is a screen capture of the prompt for choosing the transmission execution mode: Select Item(s): Quit// EXP Export Batch Indicate whether the transmission should be queued to run on the Background via TaskMan, on the Foreground (Terminal Screen) or in Debug Mode (Foreground) Select one of the following: B Background F Foreground D Debug Mode (Foreground) Running Mode: F// 6. PSO SPMP NOTIFICATIONS Mail Group --------------------------------- The existing mail group PSO SPMP NOTIFICATIONS released by PSO*7*408 will be modified from type PRIVATE to PUBLIC. 7. SPMP Transmission Failed MailMan Message ---------------------------------------- The Mailman message generated by the SPMP Scheduled Background Job as well as by the (B)ackground option mentioned above for exporting a batch to the state was modified to include Operating System sFTP Log Information, as in this example from an OpenVMS environment: Subj: NEW YORK Prescription Monitoring Program Transmission Failed [#99999] 02/29/16@12:44 26 lines From: SPMP TRANSMISSION In 'IN' basket. Page 1 -------------------------------------------------------------------------- There was a problem with the transmission of information about Controlled Substance prescriptions to the NEW YORK State Prescription Monitoring Program (SPMP). Batch #: 41 Period : 02/29/16 thru 02/29/16 Error : Secure FTP Transmission failed. Please, use the option Export Batch Processing [PSO SPMP BATCH PROCESSING] to manually transmit this batch to the state. sFTP Log: ======== $ SET VERIFY=(PROCEDURE,IMAGE) $ SET DEFAULT USER$:[SPMP] $ sftp -"D3" -oIdentityFile="/USER$/SPMP/VMSSSHID." -"B" SPMP_FTP_201606021 6.INP -oUser=VATEST 54.175.203.159 debug( 2-JUN-2016 17:37:28.02): Ssh2/SSH2.C:1896: CRTL version (SYS$SHARE:D SHR.EXE ident) is V8.3-01 debug( 2-JUN-2016 17:37:28.04): SshAppCommon/SSHAPPCOMMON.C:313: Allocating bal SshRegex context. debug( 2-JUN-2016 17:37:28.05): SshConfig/SSHCONFIG.C:3482: Metaconfig pars stopped at line 4. debug( 2-JUN-2016 17:37:28.05): SshConfig/SSHCONFIG.C:890: Setting variable rboseMode' to 'FALSE'. debug( 2-JUN-2016 17:37:28.06): SshConfig/SSHCONFIG.C:3390: Unable to open /ssh2_config debug( 2-JUN-2016 17:37:28.07): Connecting to 54.175.203.159, port 22... not used) debug( 2-JUN-2016 17:37:28.07): Ssh2/SSH2.C:2881: Entering event loop. debug( 2-JUN-2016 17:37:28.12): Ssh2Client/SSHCLIENT.C:1655: Creating tra protocol debug( 2-JUN-2016 17:37:28.12): SshAuthMethodClient/SSHAUTHMETHODC.C:104: "publickey" to usable methods. %TCPIP-E-SSH_FC_ERR_DEST, destination is not directory or does not exist ... debug( 2-JUN-2016 17:37:35.66): Ssh2/SSH2.C:327: locally_generated = TRUE Disconnected; no more authentication methods available (No further authent on methods available.). debug( 2-JUN-2016 17:37:35.66): Ssh2Client/SSHCLIENT.C:1731: Destroying debug( 2-JUN-2016 17:37:35.66): SshConfig/SSHCONFIG.C:2888: Freeing pki. pki != NULL, user_pki = NULL) debug( 2-JUN-2016 17:37:35.66): SshConnection/SSHCONN.C:2636: Destroying debug( 2-JUN-2016 17:37:35.66): Ssh2Client/SSHCLIENT.C:1799: Destroying completed. debug( 2-JUN-2016 17:37:35.66): SshAuthMethodClient/SSHAUTHMETHODC.C:109: oying authentication method array. %TCPIP-F-SSH_FATAL, non-specific fatal error condition 8. PSO SPMP ADMIN Security Key --------------------------- A new security key was created to restrict access to the following SPMP functionalities: - ASAP Definition Customization updates through the option View/Edit ASAP Definitions [PSO SPMP ASAP DEFINITIONS]. Visualization of the current ASAP Definition is not restricted. - SPMP Parameters value updates through the option View/Edit SPMP State Parameters [PSO SPMP STATE PARAMETERS]. Visualization of the current SPMP parameters is not restricted. - SSH Key generation or replacement through the option Manage Secure SHell (SSH) Keys [PSO SPMP SSH KEY MANAGEMENT]. Visualization of the current public key is not restricted. 9. Misleading "File Successfully Transmitted" message for Linux OS --------------------------------------------------------------- The previous algorithm used to identify whether the SPMP sFTP data transmission was successful was not 100% accurate for Linux Operating Systems. A new algorithm has been created and it should reflect the transmission status with much greater accuracy when transmitting data from a Linux based environment. 10.SPMP Files Access Restrictions ------------------------------ The FILE ACCESS setting for the SPMP files below will be opened up so users can use FileMan to view and search their content. The files were unintentionally released in PSO*7*408 as restricted. - SPMP ASAP RECORD DEFINITION (#58.4) - SPMP EXPORT BATCH (#58.42) 11. Pharmacy DEA Number (ASAP Data Element PHA03) --------------------------------------------- The Pharmacy DEA# was previously retrieved from the INSTITUTION file (#4) through the RELATED INSTITUTION field (#100) in the OUTPATIENT SITE file (#59). Now, the software will look for a DEA# for the institution in NPI INSTITUTION field (#101) in the OUTPATIENT SITE file (#59). If the DEA# for the NPI Institution is blank the software will retrieve the DEA# for the Related Institution, like it was doing before this patch. Patch Components ================ Files & Fields Associated: File Name (#) Field Name (#) New/Modified/Deleted ----------------- -------------------------------------- -------------------- SPMP ASAP RECORD DEFINITION (#58.4) VERSION sub-file (#58.4001) -DATA ELEMENT DELIMITER CHAR (#.02) New -SEGMENT TERMINATOR CHAR (#.03) New -END OF LINE ESCAPE CHAR(S) (#.04) New -SEGMENT sub-file (#58.40011) --LEVEL (#.06) New --DATA ELEMENT sub-file (#58.400111) ---ELEMENT VALUE (M EXPRESSION) (#.08) New SPMP STATE PARAMETERS (#58.41) ASAP VERSION (#1) Modified STATE SFTP SERVER IP ADDRESS (#7) Modified STATE SFTP SERVER USERNAME (#8) Modified SFTP TRANSMISSION MODE (#13) Modified RENAME FILE AFTER UPLOAD (#17) New SFTP SSH KEY FORMAT (#18) New SFTP SSH KEY ENCRYPTION (#19) New SFTP SSH PRIVATE KEY TEXT (#100) Modified SFTP SSH PUBLIC KEY TEXT (#200) Modified SPMP EXPORT BATCH (#58.42) PRESCRIPTIONS sub-file (#58.42001) -NDC SENT (#3) New Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- PSO SPMP ASAP DEFINITIONS Action New PSO SPMP VIEW ASAP DEFINITIONS Action Delete PSO SPMP SSH KEY MANAGEMENT Action New PSO SPMP MENU Menu Modified Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- PSO SPMP3 COPY VERSION New PSO SPMP3 CUSTOMIZE DATA ELEMENT New PSO SPMP3 CUSTOMIZE SEGMENT New PSO SPMP3 DELETE CUSTOMIZATION New PSO SPMP3 EDIT DELIMETERS New PSO SPMP3 MENU Modified PSO SPMP3 SHOW DETAILS Modified Security Keys Associated: Security Key Name New/Modified/Deleted ------------- -------------------- PSO SPMP ADMIN New Templates Associated: Template Name Type File Name (#) New/Modified/Deleted ------------- ---- ------------- -------------------- PSO SPMP VIEW ASAP DEFINITION List N/A Modified New Service Requests (NSRs): ---------------------------- 20150701 - State Prescription Monitoring Program Enhancement Patient Safety Issues (PSIs): ----------------------------- N/A Remedy/CA-SDM Ticket(s) & Overviews: ----------------------------------- N/A TEST Sites: =========== BEDFORD, MA BOSTON HCS CHEYENNE, WY HINES, IL INDIANAPOLIS, IN IRON MOUNTAIN, MI LOUISVILLE, KY MONTANA HCS NORTHAMPTON, MA SAN DIEGO, CA ST CLOUD, MN TENNESSEE VALLEY HCS Documentation Retrieval Instructions: ------------------------------------- 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. File Description File Name FTP Mode -------------------------------------------------------------------------- Outpatient Pharmacy V. 7.0 Manager's PSO_7_MAN_UM_R0816.PDF (binary) User Manual Outpatient Pharmacy V. 7.0 Technical PSO_7_TM_R0816.PDF (binary) Manual/Security Guide SPMP Enhancement Release Notes PSO_7_P451_RN.PDF (binary) SPMP Enhancement Installation Guide PSO_7_P451_IG.PDF (binary) Documentation can also be retrieved from the VA Software Documentation Library (VDL) on the Internet at the following address: http://www4.domain.ext/vdl. Patch Installation: Pre-Install Process ------------------- In order to successfully install the newly improved and customizable ASAP definition that is being distributed by this patch we will first completely delete the existing content of the SPMP ASAP RECORD DEFINITION file (#58.4) which is where the ASAP definitions are stored. Note: This step will happen automatically and no user action is required. Post-Install Process -------------------- The post-install routine PSO451PI in the patch PSO*7*451 will automatically perform a few updates related to the SPMP functionality: - The FILE ACCESS setting for the files below will be opened up so users can use FileMan to view and search their content. They were unintentionally released in PSO*7*408 as restricted. SPMP ASAP RECORD DEFINITION (#58.4) SPMP EXPORT BATCH (#58.42) - The new field/parameter RENAME FILE AFTER UPLOAD (#17) in the SPMP STATE PARAMETERS file (#58.41) will automatically be set to 1 (YES). - The parameter setting workaround for sites transmitting Appriss AWARxE will be automatically corrected the following way: Before: ======= STATE SFTP SERVER IP ADDRESS: prodpmpsftp 54.175.203.159 STATE SFTP SERVER USERNAME : -oUser=username After: ====== STATE SFTP SERVER IP ADDRESS: sftp.pmpclearinghouse.net STATE SFTP SERVER USERNAME : username@prodpmpsftp - The mail group PSO SPMP NOTIFICATIONS will be changed to type 'PUBLIC' as it was incorrectly released as 'PRIVATE' by PSO*7*408. Notes: - These updates will happen automatically and no user action is required. - The post-install routine PSO451PI will be deleted from your system upon completion of the patch installation. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Outpatient+Pharmacy/Patches/PSO_7.0_451

Patch Subject: REPORT OF CLAIMS, ZIP CODE, DENIAL LETTER, ONE WAY/ROUND TRIP, CLAIM DELETION Description: ============ This patch addresses 7 issues: 1. The Report Of Claim Amounts report is not displaying values for Special Mode claims. 2. The Bene Travel software is incorrectly displaying 9 digit zip codes. 3. The denial letter is not printing the correct user name. 4. There is duplicate wording in the denial letter template. 5. Special Mode claims are incorrectly displaying 'One Way' every time. 6. An undefined error occurs when there is single division. 7. Existing claims are being erased. Associated NSR(s): ================== N/A Associated Ticket(s): ===================== 1. INC000000840342 - Bene Travel - General: Report Showing $0.00 DUP: INC000000848649 DUP: INC000000854474 DUP: I9939495FY16 2. INC000000848999 - Bene Travel - 9 digit zip codes printing with two dashes "- -". DUP: I9940754FY16 3. INC000000966732 - Bene Travel - General: Denial Letter Print DUP: I9941631FY16 4. INC000001035335 - Bene Travel - General: Denial Letter duplicate wording DUP: INC000001231273 DUP: I9941765FY16 5. INC000001118197 - Bene Travel - General: SP Mode - Round Trip/One Way not displaying correctly DUP: I9942099FY16 6. I5637262FY15 - Bene Travel terminated sessions 7. I7382571FY16 - Bene Travel Claims are being deleted Participating Test Sites: ========================= James J. Peters VA Medical Center (Bronx, NY) VA Tennessee Valley Health Care System Veterans Health Care System of the Ozarks (Fayetteville) Ticket Overview: ================ 1. INC000000840342 - Bene Travel - General: Report Showing $0.00 Problem: -------- The 'Standard Claims Output' report in the Report of Claim Amounts [DGBT BENE TRAVEL REPORT] option is not adding the TOTAL INVOICE AMOUNT (#60) field from Special Mode claims to the $TOTAL column of the report. Resolution: ----------- Routine DGBTOA2 has been modified to use the TOTAL INVOICE AMOUNT (#60) value instead of AMOUNT PAYABLE (#10) field for when the claim type is Special Mode. 2. INC000000848999 - Bene Travel - 9 digit zip codes printing with two dashes "- -". Problem: -------- If the ZIP (#1.04) field of the INSTITUTION (#4) file contains a nine digit zip code, a hyphen is being improperly saved in the ZIP CODE/DESTINATION (#28.2) field of the BENEFICIARY TRAVEL CLAIM (#392) file. Resolution: ----------- Routine DGBTE1 has been modified to remove the hyphen from the nine digit zip code before it is saved in the ZIP CODE/DESTINATION (#28.2) field. Routines DGBTCD and DGBTCR have been modified to display the FileMan external format for the zip code. Also, created post-init routine DGBT1P28 to correct any existing zip code entries in the BENEFICIARY TRAVEL CLAIM (#392) file that contain a hyphen. 3. INC000000966732 - Bene Travel - General: Denial Letter Print Problem: -------- The Reprint Denial of Benefits Letters [DGBT REPRINT DENIAL LETTERS] option is incorrectly displaying the name of the current user, rather than the name of the user that entered the claim. Resolution: ----------- Routine DGBTDLT1 has been modified to display the name of the user that entered the claim rather than the current user. 4. INC000001035335 - Bene Travel - General: Denial Letter duplicate wording Problem: -------- The phrase "date you completed travel associated with your" is repeated in the BT Denial of Benefits Letter when "30 Day Application Requirement" is selected as the reason for denial. Resolution: ----------- The TEXT (#1) field of the "30 DAY APPLICATION REQUIREMENT" entry in the BENEFICIARY TRAVEL DENIAL REASONS (#392.8) file is modified with routine DGBT1P28 to remove the duplicate wording. The corrected version will replace the existing text in the field, even if it has already been corrected at the site. 5. INC000001118197 - Bene Travel - General: SP Mode - Round Trip/One Way not displaying correctly Problem: -------- When using the View of Claim [DGBT BENE TRAVEL VIEW] option to view a special mode claim, the "One Way/Round Trip:" prompt will always display 'One Way'. Resolution: ----------- Routine DGBTCDSP has been modified to correctly display the appropriate trip type. 6. I5637262FY15 - Bene Travel terminated sessions Problem: -------- Sites are getting an undefined error when the MULTIDIVISION MED CENTER? (#11) field in the MAS PARAMETER (#43) file is set to zero. Resolution: ----------- Modified code in routine DGBTE to prevent the undefined error when the MULTIDIVISION MED CENTER? (#11) field is set to zero. 7. I7382571FY16 - Bene Travel Claims are being deleted Problem: -------- If a clerk goes into an existing claim and then enters a "^" at the "Is this a Mileage or Special Mode Claim?: M//" prompt, all fields in the claim will be deleted. Resolution: ----------- Routine DGBTE has been modified by adding a check to see if the clerk is editing an existing claim, if so the fields in the claim will be preserved. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Beneficiary+Travel/Patches/DGBT_1.0_28

Patch Subject: VIA INCREMENT 3 UPDATES Description: ============ The VistA integration Adaptor (VIA) system is a middleware used to transport clinical and non-clinical electronic information between producing and consuming applications in VA systems. VIA utilizes remote procedure calls (RPCs) for data requested by consuming applications. The purpose of this patch is to publish RPCs that were added to the VIAB WEB SERVICES OPTION in the OPTION file (#19), RPC field (#320) thus allowing VIA access to them. This patch is one of a series of patches that will allow access for use by VIA: OR*3*433 TIU*1*306 VIAB*1*7 Three new RPCs were created to meet the needs of consuming applications. VIAB GETSURR This RPC returns information about a user's surrogate, including start/time and end date/time, if they are specified. VIAB GET USER DIVISIONS This RPC provides divisional information on the DUZ that is passed in as the input parameter. VIAB SITENAME This RPC will provide the Site Name to the calling application, given the site ID or station number is passed in. VIA was granted access to ICR #2533 by Kernel to use the function DIV4^XUSER. 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 ----------- ---- -------------------- VIAB WEB SERVICES OPTION Broker (Client/Server) Modified RPCs added to VIAB WEB SERVICES option by this patch: ORQPT PROVIDERS ORWMC PATIENT PROCEDURES1 ORWRP REPORT LISTS TIU CREATE ADDENDUM RECORD TIU UPDATE ADDITIONAL SIGNERS VIAB GET USER DIVISIONS VIAB GETSURR VIAB SITENAME Option Details: Field Value ----- ----- NAME (#.01): VIAB WEB SERVICES OPTION MENU TEXT (#1): VIAB Web Services Option DESCRIPTION (#3.5): This option is required by the Kernel Broker to give access to the RPCs used by the Vista Integration Adapter (VIA) team. New Remote Procedure Calls: -------------------------- VIAB GET USER DIVISIONS VIAB GETSURR VIAB SITENAME New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Remedy Ticket(s) & Overview: ---------------------------- N/A Test Sites: ----------- Central Alabama Veterans Health Care System VA Central Western Massachusetts HCS VA Gulf Coast Veterans Health Care System Patch Installation: ------------------- Pre/Post Installation Overview: ------------------------------- Patch VIAB*1*5 must be installed prior to installation of VIAB*1*7. Patch OR*3*433 must be installed prior to installation of VIAB*1*7. Patch TIU*1*306 must be installed prior to installation of VIAB*1*7. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/VistA+Integration+Adapter/Patches/VIAB_1.0_7

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 #1 Description: ============ NOTE: This patch is part of NDF Data Update FY17 #1, which is comprised of two patches, PSN*4*497 and PSN*4*498. 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, and products for which the national formulary restriction 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: ========================= I10930274FY17 Test Sites: =========== CENTRAL PLAINS HCS CHILLICOTHE VAMC OKLAHOMA CITY VAMC PALO ALTO HCS 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_497

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: SET NUMBER OF LABELS IN LABORATORY TEST FILE (#60) FOR EACH FACILITY Description: ============ The NSR20140714 Set Number of Labels in File 60 for Each Facility intake modification allows multidivisional facilities to set the number of labels required for each site on the VistA instance. This number is set in LABORATORY TEST File (#60). The current Lab Package functionality provides only one option for setting label requirements for all sites in a multidivisional facility. It lacks the necessary flexibility to accommodate the requirements and procedures associated with printing labels for institutions that share the same Veterans Integrated System Technology Architecture (VistA) database. This modification will be useful to multidivisional facilities because it enables customizing the number of labels required by individual institutions within a multidivisional VistA system. This modification adds the following new multiple field to the LABORATORY TEST File (#60): INSTITUTION EXTRA LABELS field (#60.15) Two new sub-fields are added to the INSTITUTION EXTRA LABELS multiple: INSTITIUTION EXTRA LABELS (#.01)b "pointer to the Institution file (#4) NUMBER OF LABELS (#1) The following two options are being updated to allow ADPACs or LIMs ()Laboratory Information Manager) to customize the number of labels for individual institutions for each lab test: Edit atomic tests [LRDIEATOMIC] Edit cosmic tests [LRDIECOSMIC] These options, LRDIECOSMIC and LRDIEATOMIC now prompt the user for the following two new fields: INSTITUTION EXTRA LABELS field (#60.15,.01). NUMBER OF LABELS subfield (#60.15,1) The LIM/ADPAC selects an available laboratory test name from the LABORATORY TEST NAME field (#60.01) and then selects the institution requiring extra labels from the list of co-located institutions to populate the INSTITUTION EXTRA LABELS field (#60.15,.01). After the laboratory test and co-located institution are selected, the number of additional labels needed is added to the NUMBER OF LABELS subfield (#60.15,1). This field specifies the number of labels, beyond the default number, set for the selected lab test at the selected institution. Each lab test can be configured individually for each co-located institution. After a lab test is configured, the specified number of extra labels designated will print each time a user at the configured institution accessions an order for a preconfigured lab test. If either the lab test, or the institution, is not configured for additional labels then the default number of labels will print. Each lab test can be configured for multiple institutions and each institution can define the necessary number of labels to print for each lab test. The new INSTITUTION EXTRA LABELS field (#16.1) takes precedence over the existing EXTRA LABELS field (#16) of the LABORATORY TEST FILE (#60). Important: The INSTITUTION EXTRA LABELS field (#60.15,.01) is connected to the national INSTITUTION File (#4). Prior to editing the fields added by this modification, ensure that co-located institutions are added to the ACCESSION AREA field (#60,6). This multiple field includes the INSTITUTION field (#60.11,.01) and the ACCESSIONING AREA subfield (#60.11,1). Enter the necessary institutions and an appropriate accessioning area for the laboratory test being edited. Note: The new fields added to LABORATORY TEST File (#60) for this modification are similar in name to existing fields, specifically the INSTITUTION field (#60.11,.01), and the EXTRA LABELS field (#60.16). Care must be exercised to ensure these fields are not confused with the new fields added with this modification when edited. Multi-Lab Test ACCESSIONING =========================== When accessioning multiple lab tests, the number of Institution Extra Labels will be accumulated for each test. So the number of extra labels printed include the following values: (1) The original default number of labels for the accessioned tests, i.e., one label per accession. -and, one of the following- (2) the number of Institution Extra Labels (field 16.1) for each test if that number is defined for the test and the division for which the user is signed in. -or- (3) the number of Extra Labels (field #16) defined for the test, if Institution Extra Labels is undefined. So, for the following example with UREA NITROGEN and GLUCOSE being accessioned together, seven (7) total labels will print. LAB TEST NAME: UREA NITROGEN INSTITUTION: INST XYZ UNIQUE ACCESSION #: NO EXTRA LABELS: 4 COLLECTION SAMLE: SERUM ACCESSION AREA: CHEMISTRY INSTITUTION EXTRA LABELS: INST XYZ # OF LABELS: null/none LAB TEST NAME: GLUCOSE INSTITUTION: INST XYZ UNIQUE ACCESSION #: NO EXTRA LABELS: null/none COLLECTION SAMLE: SERUM ACCESSION AREA: CHEMISTRY INSTITUTION EXTRA LABELS: INST XYZ # OF LABELS: 2 So, we have (four) 4 extra labels for UREA NITROGEN test and (two) 2 Institution Extra Labels for Glucose test and one label will print for the accession (under normal conditions with no extra labels). This produces 1 + 4 + 2 = seven (7) total labels. The NSR for this intake addresses the following requirement: ============================================================ VHBAO: NEED493878: As an authorized user of the laboratory suite, I need the ability to print extra accession labels printed on label stock my facility uses, so lab test results can be easily obtained and delays in patient care can be avoided. This intake has been implemented locally at the Kansas City, MO VAMC. BLOOD BANK Clearance: RISK ANALYSIS: Changes made by patch LR*5.2*465 have no effect on Blood Bank software functionality, therefore RISK is none. EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*465 does not contain any changes to the VISTA BLOOD BANK Software as defined by ProPath standard titled: BBM Team Review of VistA Patches. EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*465 does not alter or modify any software design safeguards or safety critical elements functions. VALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes made, no specific validation requirements exist as a result of installation of this patch. Patch Components: Files & Fields Associated: File Name Number Field Name Number New/Modified/Deleted LABORATORY TEST 60 INSTITUTION EXTRA LABELS 16.1 NEW INSTITUTION EXTRA LABELS .01 NEW NUMBER OF LABELS 1 NEW Options Associated: Option Menu Text Name Type New/Modified/Deleted Edit atomic tests [LRDIEATOMIC] Input (Edit Template Updated) Edit cosmic tests [LRDIECOMIC] Input (Edit Template Updated) Templates Associated: Template Name Type File Name Number New/Modified/Deleted LR ATOMIC TESTS Input Laboratory Test 60 Modified LR COSMIC TESTS Input Laboratory Test 60 Modified New Service Requests (NSRs): 20140714 Set Number of Labels in File 60 for Each Facility. Patient Safety Issues (PSIs): N/A Remedy Ticket(s) & Overview: N/A Test Sites: Information regarding the IOC test sites for NSR20140714 is available in the LR*5.2*465 Initial Operating Capability Entry Request and Exit Summary document. Software and Documentation Retrieval Instructions: Software is being released as a PackMan message. Documentation can be found in the VA Software Documentation Library at http://www4.domain.ext/vdl/. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Lab+Service/Patches/LR_5.2_465

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: VIA INCREMENT 3-B UPDATES Description: ============ The VistA integration Adaptor (VIA) system is a middleware used to transport clinical and non-clinical electronic information between producing and consuming applications in VA systems. VIA utilizes remote procedure calls (RPCs) for data requested by consuming applications. The purpose of this patch is to publish RPCs that were added to the VIAB WEB SERVICES OPTION in the OPTION file (#19), RPC field (#320). These new RPCs were created to meet the needs of consuming applications. VIAB ACTPROB This RPC returns a list of active problems for a patient. VIAB BMS This RPC supports request for data from the Bed Management System (BMS). The input parameter 'PATH' determines the data returned. VIAB CPTMODS This RPC returns a list of CPT modifiers for a given CPT Code. VIAB CURSPE This RPC returns the current observation status for a patient based on the treating specialty. VIAB DEFAULT REQUEST REASON This RPC returns a default reason for a consult service in the REQUEST SERVICES File #123.5. VIAB EDIT DEFAULT REASON This RPC returns the value of RESTRICT DEFAULT REASON EDIT field. VIAB NOTEVSTR This RPC returns VISIT LOCATION;EPISODE BEGIN DATE;VISIT TYPE from the TIU DOCUMENT file. VIAB RADSRC This RPC returns a list of active contract/sharing agreement type. These 12 existing RPCs were added to VIAB WEB SERVICES OPTION. MBAA APPOINTMENT LIST BY NAME MBAA APPOINTMENT MAKE MBAA CANCEL APPOINTMENT MBAA FACILITY WAIT LIST MBAA GET CLINIC AVAILABILITY MBAA GET CLINIC DETAILS MBAA LIST CANCELLATION REASONS MBAA PATIENT PENDING APPT MBAA PROVIDERS BY CLINIC MBAA REMOVE FROM EWL MBAA VERIFY CLINIC ACCESS MBAA WAIT LIST BY DFN 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 ----------- ---- -------------------- VIAB WEB SERVICES OPTION Broker (Client/Server) Modified RPCs added to VIAB WEB SERVICES option by this patch: MBAA APPOINTMENT LIST BY NAME MBAA APPOINTMENT MAKE MBAA CANCEL APPOINTMENT MBAA FACILITY WAIT LIST MBAA GET CLINIC AVAILABILITY MBAA GET CLINIC DETAILS MBAA LIST CANCELLATION REASONS MBAA PATIENT PENDING APPT MBAA PROVIDERS BY CLINIC MBAA REMOVE FROM EWL MBAA VERIFY CLINIC ACCESS MBAA WAIT LIST BY DFN VIAB ACTPROB SEND TO SITE VIAB BMS SEND TO SITE VIAB CPTMODS SEND TO SITE VIAB CURSPE SEND TO SITE VIAB DEFAULT REQUEST REASON SEND TO SITE VIAB EDIT DEFAULT REASON SEND TO SITE VIAB NOTEVSTR SEND TO SITE VIAB RADSRC SEND TO SITE Option Details: Field Value ----- ----- NAME (#.01): VIAB WEB SERVICES OPTION MENU TEXT (#1): VIAB Web Services Option DESCRIPTION (#3.5): This option is required by the Kernel Broker to give access to the RPCs used by the Vista Integration Adapter (VIA) team. New Remote Procedure Calls: -------------------------- VIAB ACTPROB SEND TO SITE VIAB BMS SEND TO SITE VIAB CPTMODS SEND TO SITE VIAB CURSPE SEND TO SITE VIAB DEFAULT REQUEST REASON SEND TO SITE VIAB EDIT DEFAULT REASON SEND TO SITE VIAB NOTEVSTR SEND TO SITE VIAB RADSRC SEND TO SITE New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Remedy Ticket(s) & Overview: ---------------------------- N/A Test Sites: ----------- Central Alabama Veterans Health Care System Lebanon VA Medical Center VA Gulf Coast Veterans Health Care System SFTP SOFTWARE RETRIEVAL: ======================= File Name File Description FTP Mode ------------------------------------------------------------- VIAB_1_8_Release_notes.doc Release Note binary The preferred method is to retrieve the file 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 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 Patch Installation: ------------------- Pre/Post Installation Overview: ------------------------------- Patch VIAB*1*7 must be installed prior to installation of VIAB*1*8 Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/VistA+Integration+Adapter/Patches/VIAB_1.0_8

Patch Subject: PCE IMMUNIZATION ENHANCEMENTS - INCREMENT 3 Description: ============ Note: Patch PSN*4*448 must be installed before installing patch PX*1*215. The Veterans Health Information Systems and Technology Architecture (VistA) Immunizations Enhancements (VIMM) 2.0 project, Increment 3, builds upon the file structures and standardized data introduced in Increments 1 and 2 by adding functional enhancements to the existing VistA Patient Care Encounter (PCE) package. This patch provides the following new features: 1) Creates Remote Procedure Calls (RPCs) for use by the Enterprise Health Management Platform (eHMP) project, the Computerized Patient Record System (CPRS) software, Data Access Service (DAS) and others. These RPCs retrieve immunization information from the following files: - VACCINE INFORMATION STATEMENT (#920) - IMMUNIZATION INFO SOURCE (#920.1) - IMM ADMINISTRATION ROUTE (#920.2) - IMM ADMINISTRATION SITE (BODY) (#920.3) - IMM CONTRAINDICATION REASONS (#920.4) - IMM REFUSAL REASONS (#920.5) - V IMM CONTRA/REFUSAL EVENTS (#9000010.707) - IMM MANUFACTURER (#9999999.04) - IMMUNIZATION (#9999999.14) - IMMUNIZATION LOT (#9999999.41) - IMM DEFAULT RESPONSES (#920.05) 2) Introduces functionality for capturing the reason(s) an immunization was not given by documenting immunization contraindications and/or refusal events. This functionality includes the following: - Creation of the V IMM CONTRA/REFUSAL EVENTS file (#9000010.707) - A WARNING UNTIL DATE may be stored for temporary contraindications/refusals. This is the date until which the contraindication/refusal is valid. - When an immunization for a patient is associated with valid contraindications/refusals (WARNING UNTIL DATE is not a past date), the software will display a warning and the user will be required to acknowledge the warning and enter a justification reason before continuing with administration. 3) Inactivates the functionality of the PCE CODE MAPPING file (#811.1). The file will still exist, but the mappings in the file will no longer be used to determine which related entries in the V IMMUNIZATION (#9000010.11), V SKIN TEST (#9000010.12), and V CPT (#9000010.18) files need to automatically be recorded. From now on, the mappings in the CODING SYSTEM multiple of the IMMUNIZATION (#9999999.14) and SKIN TEST (#9999999.28) files will be used for this purpose. There are a few differences with this new approach: a) The PCE CODE MAPPING file was managed locally, while the CODING SYSTEM multiple of the IMMUNIZATION and SKIN TEST files are standardized and managed nationally. b) Mappings to ICD-10 codes will now be supported. If an immunization or skin test is mapped to an ICD-10 code, when that immunization or skin test is documented, it will automatically file the mapped ICD-10 code to the V POV file (#9000010.07). c) Stop the practice of automatically recording an immunization or skin test when a corresponding CPT code is filed. The mappings will only be used to automatically file the corresponding codes (CPT and ICD-10) when an immunization or skin test is documented. However, in the reverse scenario, when a CPT code is documented, it will not automatically record the corresponding immunization or skin test. d) Codes will only automatically be filed when a VA-administered (non-historical) immunization or skin test is documented. 4) Functionality to enable a documenting provider to view some immunization prompts with default values to accept and edit the responses if needed. This functionality includes: - Creation of the IMM DEFAULT RESPONSES file (#920.05) to store facility specific default values by immunization type for ROUTE OF ADMINISTRATION, SITE OF ADMINISTRATION, DOSE, DOSE UNITS, and COMMENTS. - Creation of the Immunization Default Responses Enter/Edit menu option [PXV EDIT DEFAULT RESPONSES] gives authorized users the ability to enter or update information in the IMM DEFAULT RESPONSES file (#920.05). 5) Updates the NDC CODE (VA) field (#.18) in the IMMUNIZATION LOT file (#9999999.41) so access to information in the NDC/UPN file (#50.67) is controlled by application programmer interfaces (APIs). Patch Components: ----------------- APIs Associated: API New/Modified/Deleted ----------- -------------------- DATA2PCE^PXAPI (ICR #1889) Modified GETENC^PXAPI (ICR #1894) Modified ENCEVENT^PXKENC (ICR #1894) Modified VICR^PXPXRM (ICR #4250) New VICR^PXPXRMI1 (ICR #4519) New DQSAVE^PXRPC (ICR #6386) New IMMSTAT^PXAPIIM (ICR #6387) New Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- IMM DEFAULT RESPONSES (#920.05) FACILITY (#.01) New IMMUNIZATION (multiple field #1, sub-file #920.051) New IMMUNIZATION (#.01) of the IMMUNIZATION sub-file (#920.051) New ROUTE OF ADMINISTRATION (#1302) of the IMMUNIZATION sub-file (#920.051) New SITE OF ADMINISTRATION (#1303) of the IMMUNIZATION sub-file (#920.051) New DOSE (#1312) of the IMMUNIZATION sub-file (#920.051) New DOSE UNITS (#1313) of the IMMUNIZATION sub-file (#920.051) New COMMENTS (#81101) of the IMMUNIZATION sub-file (#920.051) New IMM CONTRAINDICATION REASONS (#920.4) CONCEPT CODING SYSTEM (#.05) Modified IMM ROUTES TO SITES (#920.6) ROUTE (#.01) New SITES (multiple field #1, sub-file #920.61) New SITES (#.01) of the SITES sub-file (#920.61) New V IMMUNIZATION (#9000010.11) WARNING ACKNOWLEDGED (#1220) New WARNING OVERRIDE REASON (#1601) New V SKIN TEST (#9000010.12) CODING SYSTEM (multiple field #3, sub-file #9000010.123) Deleted CODING SYSTEM (#.01) of the CODING SYSTEM sub-file (#9000010.123) Deleted CODE (multiple field #.02, sub-file #9000010.1231 of the CODING SYSTEM sub-file (#9000010.123) Deleted CODE (#.01) of the CODE sub-file (#9000010.1231) Deleted V IMM CONTRA/REFUSAL EVENTS (#9000010.707) CONTRAINDICATION/REFUSAL (#.01) New PATIENT NAME (#.02) New VISIT (#.03) New IMMUNIZATION (#.04) New WARN UNTIL DATE (#.05) New DATE/TIME RECORDED (#.06) New EVENT DATE AND TIME (#1201) New ENCOUNTER PROVIDER (#1204) New EDITED FLAG (#80101) New AUDIT TRAIL (#80102) New COMMENTS (#81101) New VERIFIED (#81201) New PACKAGE (#81202) New DATA SOURCE (#81203) New IMMUNIZATION LOT (#9999999.41) NDC CODE (VA) (#.18) Modified PCE CODE MAPPING N/A Modified (#811.1) 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 EDIT DEFAULT RESPONSES Run Routine New PX PCE CODE MAPPING LIST Print Modified Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- PXCE ADD/EDIT MENU Modified PXCE ICR ADD New RPCs Associated: RPC New/Modified/Deleted ------------- -------------------- PX SAVE DATA Modified PXVIMM ADMIN CODES New PXVIMM ADMIN ROUTE New PXVIMM ADMIN SITE New PXVIMM ICR LIST New PXVIMM IMM DETAILED New PXVIMM IMM FORMAT New PXVIMM IMM LOT New PXVIMM IMM MAN New PXVIMM IMM SHORT LIST New PXVIMM IMMDATA New PXVIMM INFO SOURCE New PXVIMM VICR EVENTS New PXVIMM VIS New 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): ----------------------------- PSPO #2995 PSPO #3069 Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC000001294271 R4956462FY15 R6300645FY16 Related Patient Safety Issues: ------------------------------ PSPO #2995 PSPO #3069 Problem: -------- PCE CODE MAPPING issues are causing duplicate or incorrect entries to be documented to the V IMMUNIZATION file. Resolution: ----------- The PCE CODE MAPPING file will be deprecated. Instead we will use the CODING SYSTEM multiple of the IMMUNIZATION and SKIN TEST files. 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 Clinical Reminders (PXRM) PXRM_INDEX_TM.PDF (binary) Index Technical Manual VIMM Patch PX*1*215 PX_1_P215_IG.PDF (binary) Installation Guide Patch Installation: Pre/Post Installation Overview: ------------------------------- The post-installation process will generate a report from the PCE CODE MAPPING file (#811.1) for review. The report will contain all active mappings where either a) an inactive immunization was mapped to a CPT code; or b) a CPT code was mapped to an immunization or skin test. The report will be emailed to the user who installed the patch and to the mail group specified in the REMINDER MANAGEMENT MAILGROUP field (#3) of the CLINICAL REMINDER PARAMETERS file (#800). The report will also be sent to the VHA National Center for Health Promotion and Disease Prevention (NCP) for review. If it is determined that patient charts may have been affected with erroneous data prior to the inactivating of the PCE CODE MAPPING file with this patch, the site will be contacted and instructed to submit a help desk ticket for resolution. 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_215

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: VIA INCREMENT 3-B UPDATES Description: ============ The VistA integration Adaptor (VIA) system is a middleware used to transport clinical and non-clinical electronic information between producing and consuming applications in VA systems. VIA utilizes remote procedure calls (RPCs) for data requested by consuming applications. The purpose of this patch is to publish RPCs that were added to the VIAB WEB SERVICES OPTION in the OPTION file (#19), RPC field (#320). These new RPCs were created to meet the needs of consuming applications. VIAB ACTPROB This RPC returns a list of active problems for a patient. VIAB BMS This RPC supports request for data from the Bed Management System (BMS). The input parameter 'PATH' determines the data returned. VIAB CPTMODS This RPC returns a list of CPT modifiers for a given CPT Code. VIAB CURSPE This RPC returns the current observation status for a patient based on the treating specialty. VIAB DEFAULT REQUEST REASON This RPC returns a default reason for a consult service in the REQUEST SERVICES File #123.5. VIAB EDIT DEFAULT REASON This RPC returns the value of RESTRICT DEFAULT REASON EDIT field. VIAB NOTEVSTR This RPC returns VISIT LOCATION;EPISODE BEGIN DATE;VISIT TYPE from the TIU DOCUMENT file. VIAB RADSRC This RPC returns a list of active contract/sharing agreement type. These 12 existing RPCs were added to VIAB WEB SERVICES OPTION. MBAA APPOINTMENT LIST BY NAME MBAA APPOINTMENT MAKE MBAA CANCEL APPOINTMENT MBAA FACILITY WAIT LIST MBAA GET CLINIC AVAILABILITY MBAA GET CLINIC DETAILS MBAA LIST CANCELLATION REASONS MBAA PATIENT PENDING APPT MBAA PROVIDERS BY CLINIC MBAA REMOVE FROM EWL MBAA VERIFY CLINIC ACCESS MBAA WAIT LIST BY DFN 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 ----------- ---- -------------------- VIAB WEB SERVICES OPTION Broker (Client/Server) Modified RPCs added to VIAB WEB SERVICES option by this patch: MBAA APPOINTMENT LIST BY NAME MBAA APPOINTMENT MAKE MBAA CANCEL APPOINTMENT MBAA FACILITY WAIT LIST MBAA GET CLINIC AVAILABILITY MBAA GET CLINIC DETAILS MBAA LIST CANCELLATION REASONS MBAA PATIENT PENDING APPT MBAA PROVIDERS BY CLINIC MBAA REMOVE FROM EWL MBAA VERIFY CLINIC ACCESS MBAA WAIT LIST BY DFN VIAB ACTPROB SEND TO SITE VIAB BMS SEND TO SITE VIAB CPTMODS SEND TO SITE VIAB CURSPE SEND TO SITE VIAB DEFAULT REQUEST REASON SEND TO SITE VIAB EDIT DEFAULT REASON SEND TO SITE VIAB NOTEVSTR SEND TO SITE VIAB RADSRC SEND TO SITE Option Details: Field Value ----- ----- NAME (#.01): VIAB WEB SERVICES OPTION MENU TEXT (#1): VIAB Web Services Option DESCRIPTION (#3.5): This option is required by the Kernel Broker to give access to the RPCs used by the Vista Integration Adapter (VIA) team. New Remote Procedure Calls: -------------------------- VIAB ACTPROB SEND TO SITE VIAB BMS SEND TO SITE VIAB CPTMODS SEND TO SITE VIAB CURSPE SEND TO SITE VIAB DEFAULT REQUEST REASON SEND TO SITE VIAB EDIT DEFAULT REASON SEND TO SITE VIAB NOTEVSTR SEND TO SITE VIAB RADSRC SEND TO SITE New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Remedy Ticket(s) & Overview: ---------------------------- N/A Test Sites: ----------- Central Alabama Veterans Health Care System Lebanon VA Medical Center VA Gulf Coast Veterans Health Care System SFTP SOFTWARE RETRIEVAL: ======================= File Name File Description FTP Mode ------------------------------------------------------------- VIAB_1_8_Release_notes.doc Release Note binary The preferred method is to retrieve the file 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 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 Patch Installation: ------------------- Pre/Post Installation Overview: ------------------------------- Patch VIAB*1*7 must be installed prior to installation of VIAB*1*8 Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/VistA+Integration+Adapter/Patches/VIAB_1.0_8

Patch Subject: PCE IMMUNIZATION ENHANCEMENTS - INCREMENT 3 Description: ============ Note: Patch PSN*4*448 must be installed before installing patch PX*1*215. The Veterans Health Information Systems and Technology Architecture (VistA) Immunizations Enhancements (VIMM) 2.0 project, Increment 3, builds upon the file structures and standardized data introduced in Increments 1 and 2 by adding functional enhancements to the existing VistA Patient Care Encounter (PCE) package. This patch provides the following new features: 1) Creates Remote Procedure Calls (RPCs) for use by the Enterprise Health Management Platform (eHMP) project, the Computerized Patient Record System (CPRS) software, Data Access Service (DAS) and others. These RPCs retrieve immunization information from the following files: - VACCINE INFORMATION STATEMENT (#920) - IMMUNIZATION INFO SOURCE (#920.1) - IMM ADMINISTRATION ROUTE (#920.2) - IMM ADMINISTRATION SITE (BODY) (#920.3) - IMM CONTRAINDICATION REASONS (#920.4) - IMM REFUSAL REASONS (#920.5) - V IMM CONTRA/REFUSAL EVENTS (#9000010.707) - IMM MANUFACTURER (#9999999.04) - IMMUNIZATION (#9999999.14) - IMMUNIZATION LOT (#9999999.41) - IMM DEFAULT RESPONSES (#920.05) 2) Introduces functionality for capturing the reason(s) an immunization was not given by documenting immunization contraindications and/or refusal events. This functionality includes the following: - Creation of the V IMM CONTRA/REFUSAL EVENTS file (#9000010.707) - A WARNING UNTIL DATE may be stored for temporary contraindications/refusals. This is the date until which the contraindication/refusal is valid. - When an immunization for a patient is associated with valid contraindications/refusals (WARNING UNTIL DATE is not a past date), the software will display a warning and the user will be required to acknowledge the warning and enter a justification reason before continuing with administration. 3) Inactivates the functionality of the PCE CODE MAPPING file (#811.1). The file will still exist, but the mappings in the file will no longer be used to determine which related entries in the V IMMUNIZATION (#9000010.11), V SKIN TEST (#9000010.12), and V CPT (#9000010.18) files need to automatically be recorded. From now on, the mappings in the CODING SYSTEM multiple of the IMMUNIZATION (#9999999.14) and SKIN TEST (#9999999.28) files will be used for this purpose. There are a few differences with this new approach: a) The PCE CODE MAPPING file was managed locally, while the CODING SYSTEM multiple of the IMMUNIZATION and SKIN TEST files are standardized and managed nationally. b) Mappings to ICD-10 codes will now be supported. If an immunization or skin test is mapped to an ICD-10 code, when that immunization or skin test is documented, it will automatically file the mapped ICD-10 code to the V POV file (#9000010.07). c) Stop the practice of automatically recording an immunization or skin test when a corresponding CPT code is filed. The mappings will only be used to automatically file the corresponding codes (CPT and ICD-10) when an immunization or skin test is documented. However, in the reverse scenario, when a CPT code is documented, it will not automatically record the corresponding immunization or skin test. d) Codes will only automatically be filed when a VA-administered (non-historical) immunization or skin test is documented. 4) Functionality to enable a documenting provider to view some immunization prompts with default values to accept and edit the responses if needed. This functionality includes: - Creation of the IMM DEFAULT RESPONSES file (#920.05) to store facility specific default values by immunization type for ROUTE OF ADMINISTRATION, SITE OF ADMINISTRATION, DOSE, DOSE UNITS, and COMMENTS. - Creation of the Immunization Default Responses Enter/Edit menu option [PXV EDIT DEFAULT RESPONSES] gives authorized users the ability to enter or update information in the IMM DEFAULT RESPONSES file (#920.05). 5) Updates the NDC CODE (VA) field (#.18) in the IMMUNIZATION LOT file (#9999999.41) so access to information in the NDC/UPN file (#50.67) is controlled by application programmer interfaces (APIs). Patch Components: ----------------- APIs Associated: API New/Modified/Deleted ----------- -------------------- DATA2PCE^PXAPI (ICR #1889) Modified GETENC^PXAPI (ICR #1894) Modified ENCEVENT^PXKENC (ICR #1894) Modified VICR^PXPXRM (ICR #4250) New VICR^PXPXRMI1 (ICR #4519) New DQSAVE^PXRPC (ICR #6386) New IMMSTAT^PXAPIIM (ICR #6387) New Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- IMM DEFAULT RESPONSES (#920.05) FACILITY (#.01) New IMMUNIZATION (multiple field #1, sub-file #920.051) New IMMUNIZATION (#.01) of the IMMUNIZATION sub-file (#920.051) New ROUTE OF ADMINISTRATION (#1302) of the IMMUNIZATION sub-file (#920.051) New SITE OF ADMINISTRATION (#1303) of the IMMUNIZATION sub-file (#920.051) New DOSE (#1312) of the IMMUNIZATION sub-file (#920.051) New DOSE UNITS (#1313) of the IMMUNIZATION sub-file (#920.051) New COMMENTS (#81101) of the IMMUNIZATION sub-file (#920.051) New IMM CONTRAINDICATION REASONS (#920.4) CONCEPT CODING SYSTEM (#.05) Modified IMM ROUTES TO SITES (#920.6) ROUTE (#.01) New SITES (multiple field #1, sub-file #920.61) New SITES (#.01) of the SITES sub-file (#920.61) New V IMMUNIZATION (#9000010.11) WARNING ACKNOWLEDGED (#1220) New WARNING OVERRIDE REASON (#1601) New V SKIN TEST (#9000010.12) CODING SYSTEM (multiple field #3, sub-file #9000010.123) Deleted CODING SYSTEM (#.01) of the CODING SYSTEM sub-file (#9000010.123) Deleted CODE (multiple field #.02, sub-file #9000010.1231 of the CODING SYSTEM sub-file (#9000010.123) Deleted CODE (#.01) of the CODE sub-file (#9000010.1231) Deleted V IMM CONTRA/REFUSAL EVENTS (#9000010.707) CONTRAINDICATION/REFUSAL (#.01) New PATIENT NAME (#.02) New VISIT (#.03) New IMMUNIZATION (#.04) New WARN UNTIL DATE (#.05) New DATE/TIME RECORDED (#.06) New EVENT DATE AND TIME (#1201) New ENCOUNTER PROVIDER (#1204) New EDITED FLAG (#80101) New AUDIT TRAIL (#80102) New COMMENTS (#81101) New VERIFIED (#81201) New PACKAGE (#81202) New DATA SOURCE (#81203) New IMMUNIZATION LOT (#9999999.41) NDC CODE (VA) (#.18) Modified PCE CODE MAPPING N/A Modified (#811.1) 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 EDIT DEFAULT RESPONSES Run Routine New PX PCE CODE MAPPING LIST Print Modified Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- PXCE ADD/EDIT MENU Modified PXCE ICR ADD New RPCs Associated: RPC New/Modified/Deleted ------------- -------------------- PX SAVE DATA Modified PXVIMM ADMIN CODES New PXVIMM ADMIN ROUTE New PXVIMM ADMIN SITE New PXVIMM ICR LIST New PXVIMM IMM DETAILED New PXVIMM IMM FORMAT New PXVIMM IMM LOT New PXVIMM IMM MAN New PXVIMM IMM SHORT LIST New PXVIMM IMMDATA New PXVIMM INFO SOURCE New PXVIMM VICR EVENTS New PXVIMM VIS New 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): ----------------------------- PSPO #2995 PSPO #3069 Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC000001294271 R4956462FY15 R6300645FY16 Related Patient Safety Issues: ------------------------------ PSPO #2995 PSPO #3069 Problem: -------- PCE CODE MAPPING issues are causing duplicate or incorrect entries to be documented to the V IMMUNIZATION file. Resolution: ----------- The PCE CODE MAPPING file will be deprecated. Instead we will use the CODING SYSTEM multiple of the IMMUNIZATION and SKIN TEST files. 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 Clinical Reminders (PXRM) PXRM_INDEX_TM.PDF (binary) Index Technical Manual VIMM Patch PX*1*215 PX_1_P215_IG.PDF (binary) Installation Guide Patch Installation: Pre/Post Installation Overview: ------------------------------- The post-installation process will generate a report from the PCE CODE MAPPING file (#811.1) for review. The report will contain all active mappings where either a) an inactive immunization was mapped to a CPT code; or b) a CPT code was mapped to an immunization or skin test. The report will be emailed to the user who installed the patch and to the mail group specified in the REMINDER MANAGEMENT MAILGROUP field (#3) of the CLINICAL REMINDER PARAMETERS file (#800). The report will also be sent to the VHA National Center for Health Promotion and Disease Prevention (NCP) for review. If it is determined that patient charts may have been affected with erroneous data prior to the inactivating of the PCE CODE MAPPING file with this patch, the site will be contacted and instructed to submit a help desk ticket for resolution. 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_215

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: 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: MCCF EDI TAS EBILLING BUILD 3/4 DENTAL Description: ============ Important Note: In production, there is one **MANDATORY** pre-installation activity associated with this install. The Integrated Billing (IB) Staff MUST empty the 837 extract/transmission queue PRIOR to the installation of this patch. Please reference instructions from the Pre/Post Installation Overview for further details. IB is a software module within Veterans Health Information Systems and Technology Architecture (VistA) that provides the ability for billing personnel to submit claims in either a paper or electronic format to third-party payers. The following features of the IB software will be affected by this patch: * Dental Claims The IB package currently has the ability to send proprietary professional and institutional medical claims to the Financial Services Center (FSC). These claims contain data that is used by FSC to create compliant X12N/005010X222 Health Care Claim (837P) and X12N/005010X223 Health Care Claim (837I) transactions. This patch enhances the IB package to create proprietary 837 dental claims with the data necessary to send FSC a transaction it can map to a X12N/005010X224 Health Care Claim (837D) when a user authorizes a dental claim. Dental claims will only be Transmitted electronically and cannot be printed at this time. This enhancement touched all aspects of the claims billing process. * Two minor prior defects were also addressed as part of this patch. The first occurred when a claim was on both the CSA - Claims Status Awaiting Resolution [IBCE CLAIMS STATUS AWAITING] and the CBW - COB Management Worklist [IBCE COB MANAGEMENT] worklists. If a biller tried to address on the CSA first, an error message would display and the user session would unexpectedly end. The second error occurred when a user selected Print MRA from the CBW but entered "^" instead of selecting a claim. The option abruptly ended and has been changed to instead gracefully exit. Patch Components ================ Files & Fields Associated: File Name (#) New/Modified/ Sub-file Name (#) Field Name (Number) Deleted ------------------- --------------------------------- ------------- INSURANCE COMPANY (#36) CLAIMS (DENTAL) STREET ADDR 1 New (#.191) CLAIMS (DENTAL) PHONE NUMBER New (#.1911) CLAIMS (DENTAL) STREET ADDR 2 New (#.192) BLANK (#.193) New CLAIMS (DENTAL) PROCESS CITY New (#.194) CLAIMS (DENTAL) PROCESS STATE New (#.195) CLAIMS (DENTAL) PROCESS ZIP (#.196) New CLAIMS (DENTAL) COMPANY NAME New (#.197) ANOTHER CO. PROC DENT CLAIMS? New (#.198) CLAIMS (DENTAL) FAX (#.199) New EDI ID NUMBER - DENTAL (#3.15) New 277EDI ID NUMBER sub-file (#36.017) 277EDI TYPE (#.03) Modified IB ERROR (#350.8) New Entries IB SITE PARAMETERS (#350.9) MULTIPLE FORM TYPES (#1.22) Modified DENTAL ENABLED? (#8.2) New BILL FORM TYPE (#353) New Entry Screen: I Y=7 TYPE OF SERVICE (#353.2) New Entries IB ATTACHMENT REPORT TYPE (#353.3) New Entry EDI TRANSMISSION BATCH (#364.1) BILL TYPE (#.06) Modified IB EDI TRANSMISSION RULE (#364.4) FORM TYPE (#.05) Modified IB DATA ELEMENT DEFINITION (#364.5) New/Modified Screen: I $$INCLUDE^IBY592PR(5,Y) Entries IB FORM SKELETON DEFINITION (#364.6) New/Modified Screen: I $$INCLUDE^IBY592PR(6,Y) Entries IB FORM FIELD CONTENT (#364.7) New/Modified Screen: I $$INCLUDE^IBY592PR(7,Y) Entries BILL/CLAIMS (#399) FORM TYPE (#.19) Modified BANDING DATE (#92) New TREATMENT MONTHS COUNT (#93) New TREATMENT MONTHS REMAINING (#94) New TREATMENT INDICATOR (#95) New DENTAL CLAIM NOTE (#97) New ATTACHMENT REPORT TYPE (#285) Modified PROVIDER sub-file (#399.0222) FUNCTION (#.01) Modified PROCEDURES sub-file (#399.0304) ORAL CAVITY DESIGNATION (1) New (#90.01) ORAL CAVITY DESIGNATION (2) New (#90.02) ORAL CAVITY DESIGNATION (3) New (#90.03) ORAL CAVITY DESIGNATION (4) New (#90.04) ORAL CAVITY DESIGNATION (5) New (#90.05) PROSTHESIS/CROWN/INLAY CODE New (#90.06) PRIOR PLACEMENT DATE QUALIFIER New (#90.07) PRIOR PLACEMENT DATE (#90.08) New ORTHODONTIC BANDING DATE (#90.09) New ORTHO BANDING REPLACEMENT DATE New (#90.1) TREATMENT START DATE (#90.11) New TREATMENT COMPLETION DATE (#90.12) New LINE PROVIDER sub-file (#399.0404) LINE FUNCTION (#.01) Modified OCCURRENCE CODE sub-file (#399.041) OCCURRENCE CODE (#.01) Modified TOOTH NUMBER sub-file (#399.096) New TOOTH INFORMATION sub-file (#399.30491) New TOOTH CODE (#.01) New TOOTH SURFACE (1) (#.02) New TOOTH SURFACE (2) (#.03) New TOOTH SURFACE (3) (#.04) New TOOTH SURFACE (4) (#.05) New TOOTH SURFACE (5) (#.06) New DENTAL TREATMENT PLAN ENTRY (#.07) New Bulletins Associated: New/Modified/ Bulletin Name Deleted ------------- ------------- N/A Dialogs Associated: New/Modified/ Dialog Name Deleted ----------- ------------- N/A Forms Associated: New/Modified/ Form Name File Name (Number) Deleted --------- ------------------ ------------- N/A Functions Associated: New/Modified/ Function Name Deleted ------------- ------------- N/A HL Logical Link: New/Modified/ HL Logical Name Deleted --------------- ------------- N/A HL7 Application Parameters: New/Modified/ HL7 Parameter Name Deleted ------------------ ------------- N/A HLO Application Registry: New/Modified/ HLO Registry Name Deleted ----------------- ------------- N/A Help Frames Associated: New/Modified/ Help Frame Name Deleted --------------- ------------- N/A Mail Groups Associated: New/Modified/ Mail Group Name Deleted --------------- ------------- N/A Options Associated: 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: Protocol Name SEND/ATTACH ------------- ------------- IBCNS QUIT ATTACH TO MENU IBCNSC INS CO (IN)ACTIVATE COMPANY ATTACH TO MENU IBCNSC INS CO ADDRESSES SEND TO SITE IBCNSC INS CO APPEALS OFFICE SEND TO SITE IBCNSC INS CO ASSOCIATION ATTACH TO MENU IBCNSC INS CO BILLING ADDRESSES SEND TO SITE IBCNSC INS CO BILLING PARAMETERS ATTACH TO MENU IBCNSC INS CO CHANGE COMPANY ATTACH TO MENU IBCNSC INS CO DELETE COMPANY ATTACH TO MENU IBCNSC INS CO DENTAL CLAIMS OFFICE SEND TO SITE IBCNSC INS CO EDIT ALL ATTACH TO MENU IBCNSC INS CO INPT CLAIMS SEND TO SITE IBCNSC INS CO INQUIRY OFFICE SEND TO SITE IBCNSC INS CO MAIN MAILING ADDRESS SEND TO SITE IBCNSC INS CO OPT CLAIMS SEND TO SITE IBCNSC INS CO PAYER ATTACH TO MENU IBCNSC INS CO REMARKS ATTACH TO MENU IBCNSC INS CO RX CLAIMS ATTACH TO MENU IBCNSC INS CO SYNONYMS ATTACH TO MENU IBCNSC INSURANCE CO SEND TO SITE IBCNSC PROVIDER ID PARAMETERS ATTACH TO MENU IBCNSJ INS CO PLANS ATTACH TO MENU IBJ EXIT ATTACH TO MENU 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 ------------- ---- ------------------ ------------- IB SCREEN10H Input BILL/CLAIMS (#399) Modified IB SCREEN5 Input BILL/CLAIMS (#399) Modified IB SCREEN8 Input BILL/CLAIMS (#399) Modified IBEDIT INS CO1 Input INSURANCE COMPANY (#36) Modified Templates, List Associated: New/Modified/ Template Name Type Deleted ------------- ---- ------------- IBCE INSCO ID List Modified MAINT IBCE PRVPRV MAINT List Modified IBCE VIEW PREV List Modified TRANS1 IBCE VIEW PREV List Modified TRANS2 IBCNS INSURANCE List Modified COMPANY IBCNSC INSURANCE List New CO ADDRESSES 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) ---------------------------- None Patient Safety Issues (PSIs) ----------------------------- None Defect Tracking System Ticket(s) & Overview ------------------------------------------- N/A Test Sites: ---------- ALBUQUERQUE, NM BIRMINGHAM, AL HEARTLAND-WEST HCS MARTINSBURG, WV TOMAH, WI 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: 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 FTP Mode ----------------------------------------------------------------------- Deployment, Installation, IB_2_0_P592_IG.PDF Binary Back-out, and Rollback Guide (IB*2.0*592) EDI User Guide IB_2_0_P592_EDI_UG.PDF Binary Integrated Billing (IB) V.2.0 IB_2_0_P592_TM.PDF Binary Technical Manual Patch Installation: Pre/Post Installation Overview ------------------------------ ************************************************************************* * IMPORTANT NOTE * * In PRODUCTION, there is one **MANDATORY** pre-installation activity * * associated with this install. * * * * The IB Staff MUST empty the 837 extract/transmission queue PRIOR to * * the installation of this patch. * ************************************************************************* INSTRUCTIONS ON HOW TO EMPTY THE 837 EXTRACT TRANSMISSION QUEUE: =============================================================== The site Information Resource Management (IRM) MUST coordinate with the Billing Department to ensure that the 837 extract/transmission queue is empty. Once the Billing Department has completed the instructions, the Billing department is to inform IRM that the patch installation may proceed. The instructions to empty the queue are as follows: Select the option: TRANSMIT EDI BILLS - MANUAL [IBCE 837 MANUAL TRANSMIT] What is the purpose of this option? This option is used to by-pass the normal daily/nightly transmission queues if the need arises to get the claim to the payer quickly. When is this option used? There are occasions when there is a need to transmit a claim(s) immediately instead of waiting for the batching frequency as scheduled in the MCCR Site Parameter. This option will allow sending individual claim(s) or all claims in a ready for extract status. Upon selecting this option, you will be prompted with the following: Select one of the following: A Transmit (A)LL bills in READY FOR EXTRACT status S Transmit only (S)ELECTED bills You should select 'A' for ALL There are no other mandatory pre-installation activities associated with this patch. ------------------------------------------------------------------------ The Pre-install routine (IBY592PR) will automatically do the following: * Update entries used by the Forms Output Utility [IBCE OUTPUT FORMATTER]. * Archive BILL FORM TYPE file (#353) Internal Entry Number (IEN) 7 so as not to impact the new dental form. The BILL FORM TYPE file is a national file, but was found to include some entries at 3 VAMCs which need to be safely moved to another IEN (207). The Post-install routine (IBY592PO) will automatically do the following: * Add new entries to IB ERROR (#350.8) file * Add new entries to TYPE OF SERVICE (#353.2) file * Add new entry to IB ATTACHMENT REPORT TYPE (#353.3) file * Recompile the Input Templates for the billing screens * Set default processing of dental claims to YES - IB SITE PARAMETERS (#350.9) File, DENTAL ENABLED? (#8.2) Field. Routines IBY592PO and IBY592PR may be manually deleted by upon completion of the installation. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages

Patch Subject: ENROLLMENT SYSTEM MODERNIZATION (ESM) EARLY SEPARATION REASON Description: ============ Patch DG*5.3*947 is being released to support the enhancements for the Enterprise Health Benefits Determination (EHBD) program that focuses on updates for the Enrollment System Modernization (ESM) Phase 2 project, which supports Enrollment System Community Care (ESCC). DG*5.3*947 is also being released in support of the Enrollment System (ES) 5.3 release. Refer to Informational Patch EAS*1*165 (Enrollment Application System) for additional details regarding the ES release. The REASON FOR EARLY SEPARATION (#.09) field within the MILITARY SERVICE EPISODE (.3216) multiple within the PATIENT (#2) file is added in Veterans Health Information System and Technology Architecture (VistA) Registration, Eligibility & Enrollment (REE). The data for this field will be received from ES in ORF-Z11/ORU-Z11 HL7 messages in the ZMH segment. The Reason for Early Separation cannot be edited or deleted by VistA users and will not be sent back to ES in a Z07 message. Note: DBIA 5783 MILITARY SERVICE EPISODE API - DGMSEUTL includes component GETMSE that returns all records in the MILITARY SERVICE EPISODE (#.3216) multiple within the PATIENT (#2) file in the MSE array. While no modifications were made to this component, the REASON FOR EARLY SEPARATION (#.09) field is included in the returned array. Listing of Updates ================== This patch makes the following enhancements to REE: 1. The REASON FOR EARLY SEPARATION (#.09) field within the MILITARY SERVICE EPISODE (#.3216) multiple within the PATIENT (#2) file is added. 2. The FUTURE DISCHARGE DATE (#.08) field within the MILITARY SERVICE EPISODE (#.3216) multiple within the PATIENT (#2) file is modified to be NONEDITABLE. 3. The HL7 interface with ES is modified to include the additional data element of "REASON FOR EARLY SEPARATION" that is associated with each MSE. The ORU-Z11 message contains a new sequence, #9, in the ZMH segment for the "REASON FOR EARLY SEPARATION". 4. MSEs that contain a REASON FOR EARLY SEPARATION will not be included in the ORU-Z07 or ORF-Z07 messages sent to ES. 5. The following VistA menu options were modified to display the Reason for Early Separation: a. View Registration Data [DG REGISTRATION VIEW] b. Load/Edit Patient Data [DG LOAD PATIENT DATA] c. Register a Patient [DG REGISTER PATIENT] d. Eligibility Verification [DG ELIGIBILITY VERIFICATION] e. Preregister a Patient [DGPRE PRE-REGISTER OPTION] f. Admit a Patient [DG ADMIT PATIENT] Note: In the Preregister a Patient [DGPRE PRE-REGISTER OPTION] option, the field is shown only if there are MSE inconsistencies in the record. 6. The VistA REE system displays the Reason for Early Separation on the following screens as view-only next to the caption "Early Separation Reason:" (screen mockups below): a. Military Service Data, Screen <6> b. Military Service Data, Screen <6.1> BEGIN SCREEN CAPTURE #1 MILITARY SERVICE DATA, SCREEN <6> DGPATIENT,ONE; 666-04-1041 NSC VETERAN ========================================================================== [1] Service Branch/Component Service # Entered Separated Discharge ------------------------ --------- ------- --------- --------- NAVY/REGULAR 666041041 02/29/2000 UNKNOWN UNKNOWN MARINE CORPS/RESERVE UNKNOWN 01/28/2000 02/05/2000 HONORABLE COAST GUARD 666041041 01/07/2000 01/20/2000 HONORABLE Early Separation Reason: DISABILITY, SEVERANCE PAY, NON COMBAT (ENHANCED) <more episodes> [2] Conflict Locations: < None Specified > [3] Environment Factors: < None Specified > [4] POW: NO From: To: War: [5] Combat: From: To: Loc: [6] Mil Disab Retirement: Dischrg Due to Disab: [7] Dent Inj: Teeth Extracted: [8] Purple Heart: <RET> to CONTINUE, 1-8 or ALL to EDIT, ^N for screen N or '^' to QUIT: END SCREEN CAPTURE #1 BEGIN SCREEN CAPTURE #2 Military Service Jun 15, 2018@13:00:39 Page: 1 of 2 MILITARY SERVICE DATA, SCREEN <6.1> Patient: DGPATIENT,ONE (1041) NSC VETERAN Service Branch/Component Service # Entered Separated Discharge -------------------------------------------------------------------------- [1] NAVY/REGULAR 666041041 02/29/2000 UNKNOWN UNKNOWN [2] MARINE CORPS/RESERVE UNKNOWN 01/28/2000 02/05/2000 HONORABLE [3] COAST GUARD 666041041 01/07/2000 01/20/2000 HONORABLE Early Separation Reason: DISABILITY, SEVERANCE PAY, NON COMBAT (ENHANCED) [4] AIR FORCE/REGULAR 666041041 01/01/2000 01/05/2000 HONORABLE Early Separation Reason: DISABILITY, OTHER [5] AIR FORCE/REGULAR 666041041 06/30/1979 07/31/1989 HONORABLE + Enter ?? for more actions AD Add DE Delete ED Edit VH View History Select Action:Next Screen// END OF SCREEN CAPTURE #2 7. The VistA REE system does not display the Reason for Early Separation caption if one does not exist for the MSE. 8. The VistA REE system does not allow the user to edit an MSE Reason for Early Separation. 9. The VistA REE system does not allow the user to delete an MSE Reason for Early Separation. 10. When the number of MSEs spans multiple pages on screen <6> or screen <6.1> the VistA REE system displays all the data elements for each MSE on the same page. The MSE data elements to be displayed together include the following: Branch, Component, Service #, Entered, Separated, Discharge Type, and Future Discharge Date or Reason for Early Separation. Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- PATIENT (#2) MILITARY SERVICE Modified EPISODE (#.3216) FUTURE DISCHARGE Modified DATE (#.08) REASON FOR EARLY New SEPARATION (#.09) Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: N/A New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- N/A Problem: -------- N/A Resolution: ----------- N/A Test Sites: ----------- C.W. Bill Young VA Medical Center, Bay Pines, FL Lebanon VA Medical Center, Lebanon, PA VA Western New York Healthcare System, Buffalo, NY Software and Documentation Retrieval Instructions: ---------------------------------------------------- This software is being released as a patch (PackMan) message. Updated documentation describing the new functionality introduced by this patch is available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ Title File Name SFTP Mode -------------------------------------------------------------------------- Release Notes DG_5_3_947_RN.PDF (binary) User Manual - Registration Menu DG_5_3_947_REG_UM.PDF (binary) IVM Technical Manual IVM_2_TM_RES.PDF (binary) Patch Installation: Pre/Post Installation Overview ------------------------------ N/A Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages

Patch Subject: PMI MAPPING - FY17 #1 Description: ============ NOTE: This patch is part of NDF Data Update FY17 #1, which is comprised of two patches, PSN*4*497 and PSN*4*498. 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: ========================== I10930274FY17 Test Sites: =========== CENTRAL PLAINS HCS CHILLICOTHE VAMC OKLAHOMA CITY VAMC PALO ALTO HCS 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_498

Patch Subject: JLV Description: ============ This document describes MAG*3.0*170, the VIX Image Viewer patch. This patch adds a Zero footprint HTML5 based image viewer to the VIX to support viewing images in VA Web Applications such as eHMP and JLV. Major changes for this patch are summarized below. For detailed information, refer to the change summary on page 3. MAG*3.0*170 contains the following new features: New VIX services that support image pre-processing and image viewing in a web browser. A VIX configuration option that does not require a corresponding VistA instance. This configuration is called a relay VIX or rVIX and is co-located with the eHMP or JLV web servers to supply study metadata from a close proximity. An HTML5 Zero Footprint image viewer that can be invoked by client software interacting with any VIX instance. Patch Components: ================ This patch includes the following files: File Name Description ========= =========== MAG3_0P170.KID KIDS (Kernel Installation & Distribution System) package to be installed on the VistA System. MAG3_0P170_VIX_Setup.msi Installation file for the VIX software. MAG3_0P170_Patch_Description.pdf This document MAG3_0P170_VIX_Installation_Guide.pdf VIX Installation Guide for this patch. Documentation: ============= This document 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): =========================== This project is initiated by Requirement BR 8.0 of the Health Information Exchange Viewer BRD #1-02-03-05-08-003. Patient Safety Issues (PSIs): ============================ There are no patient safety issues associated with this patch. Defect Tracking System Ticket(s) & Overview: =========================================== 1. 354112 Larger Studies Problem: ------- Larger study is taking a long time to load the images Resolution: ---------- Issue with larger study load time resolved in this patch. 2. 437547 Pan Function Problem: ------- Pan functionality exhibited extensive lag and inadequate image adjustment with each user action. Resolution: ---------- Issue with pan functionality resolved in this patch. 3. 437552 Hard to view PDF documents Problem: ------- The zoom button is difficult to use. The experience improves with "Fit to Window" option, but no scrolling is available to access the entire image area. Resolution: ---------- Issue with PDF documents resolved in this patch. 4. 464629 FPS notation Problem: ------- Users see no reason for the FPS notation to exist when the study has no purpose for Cine. Resolution: ---------- Issue with FPS notation is fixed and the FPS notation no longer appears on studies where it has no purpose. 5. 464632 Progress Bar Problem: ------- Progress bar is not close to accurate during the image loading process. The progress bar always ends partially done. Resolution: ---------- Issue with progress bar is resolved in this patch. The progress bar is removed. 6. 464651 Window/Level Problem: ------- The Window/Level function does not always work properly. Resolution: ---------- Issue with Window/Level function is resolved in this patch. Associated Patches: ================== MAG*3.0*162 KIDS must be installed before installing MAG*3.0*170 KIDS. 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: https://www4.domain.ext/vdl/ Patch Installation: ================== Pre/Post Installation Overview: ============================== Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Imaging/Patches/MAG_3.0_170

Patch Subject: Data Access Control Description: ============ This patch releases the new Data Access Control (DAC) utility. DAC is an attribute-based access control tool, that can permit or deny a user access to a resource (i.e., a record in a file). Pre-defined target attribute values are used to match appropriate access policies to the action being taken. Policies are made up of rules that can be combined as needed, allowing for creation of simple or very complex access policies. See the VA FileMan Data Access Control User Guide for details on setting up and applying access control policies. This patch also fixes an issue with Language file (#.85) changes made to the DIR Reader in VA FileMan version 22.2, which altered the global reference and could cause an error on return to the calling application. Patch Components: ----------------- Files & Fields Associated: New/Modified/ File Name (#) Field Name (#) Deleted ------------- -------------- -------------- Policy (#1.6) New Application Action (#1.61) New Policy Function (#1.62) New Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- DIAC POLICY 1.6 New DIAC RULE 1.6 New DIAC SET 1.6 New Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- DIAC ACTIONS Action New DIAC DELETE Action New DIAC DISABLE Action New DIAC EDIT Action New DIAC FUNCTIONS Action New DIAC PRINT Action New DIAC TEST Action New DIACCESS Menu New DIOTHER Menu Modified Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- DIAC ACTION MENU New DIAC BLANK LINE New DIAC CHANGE New DIAC DELETE New DIAC DISABLE New DIAC EDIT New DIAC EXPAND New DIAC FUNCTIONS New DIAC INQUIRE New DIAC LINK ACTION New DIAC MEMBERS New DIAC QUIT New DIAC TEST New Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------------- -------------------- DIAC ACTIONS Print Application Action (#1.61) New Additional Information: ----------------------- List Template DIAC POLICY EDITOR New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. Ticket R12680330FY17 Ticket R12874559FY17 Ticket R13073003FY17 Problem: -------- VA FileMan 22.2 expanded use of the Language file #.85 and converted all hard-coded strings to the Dialog framework, to enable table-driven translation. As a result the DIR Reader now checks the Language file before issuing a prompt, which changes the current global reference. After return to the calling application, a naked global reference could now cause an undefined error. Resolution: ----------- The DIR Reader has been modified to preserve the global reference. Blood Bank Clearance: --------------------- EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch DI*22.2*8 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*8 have no effect on Blood Bank software functionality, therefore RISK is none. 3/24/2017 Test Sites: ----------- North Florida/South Georgia HCS West Palm Beach, FL Software and Documentation Retrieval Instructions: -------------------------------------------------- Updated documentation is on the VA Software Documentation Library at: http://www.domain.ext/vdl/ Title File Name SFTP Mode ---------------------------------------------------------------------- FM 22.2 Data Access Control User Guide fm22_2p8_dac_ug.PDF binary FM 22.2 Developer's Guide fm22_2dg.PDF binary FM 22.2 Technical Manual fm22_2tm.PDF binary Backout and Rollback Procedure: ------------------------------- During the VistA Installation Procedure of the KIDS build, the installer should use the 'Backup a Transport Global' action (step 3a in the Installations Instructions below). If rollback/backout is required, the installer can use the MailMan message to restore routines that were saved prior to installing the patch. The option menu DIACCESS may be disabled by using VA FileMan to assign an Out of Order message: VA FileMan 22.2 Select OPTION: 1 ENTER OR EDIT FILE ENTRIES Input to what File: OPTION// (11330 entries) EDIT WHICH FIELD: ALL// OUT OF ORDER MESSAGE THEN EDIT FIELD: Select OPTION NAME: DIACCESS Data Access Control OUT OF ORDER MESSAGE: ROLLBACK PATCH DI*22.2*8 Select OPTION NAME: Patch Installation: Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/VA+FileMan/Patches/DI_22.2_8

Patch Subject: VIX IMAGE VIEWER Description: ============ This document describes MAG*3.0*177, the VIX Image Viewer patch. This patch adds enhancements to the Zero footprint HTML5 based image viewer. Major changes for this patch are summarized below. MAG*3.0*177 contains the following new features: -General viewer improvements -Ability to hide and turn off automatic detection of Scout Images -A new menu option to view color channels of an image and compare them in dual stack view -Scout lines viewable across multiple series when viewing a cross sectional study -2 Factor Authentication support for DICOM importer -Java Version 1.8.121 -Tomcat Version 8.0.45 Associated patches: ------------------- MAG*3.0*170 KIDS must be installed before installing MAG*3.0*177 KIDS. Patch Components: ----------------- This patch includes the following files: File Name Description --------- -------------------------------------- MAG3_0P177.KID KIDS (Kernel Installation & Distribution System) package to be installed on the VistA System MAG3_0P177_VIX_Setup.msi Installation filed for the VIX software MAG3_0P177_Patch_Description.pdf This document MAG3_0P177_VIX_Installation_Guide.pdf VIX Installation Guide for this patch MAG_VIX_Admin_Guide.pdf VIX Admin Guide This patch requires the following versions: Apache Tomcat: 8.0.45 Java: 1.8.0_121 Documentation: ============== This document provides an overview, explains the changes, and outlines the installation for this patch. Files & Fields Associated: -------------------------- File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- There are no files or fields associated with this patch. Forms Associated: ----------------- Form Name File # New/Modified/Deleted ------------ ------------------- -------------------- There are no forms associated with this patch. Mail Groups Associated: ----------------------- Mail Group Name New/Modified/Deleted --------------- --------------------- There are no mail groups associated with this patch. Options Associated: ------------------- Option Name Type New/Modified/Deleted ----------- --------- -------------------- There are no options associated with this patch. Protocols Associated: --------------------- Protocol Name New/Modified/Deleted ------------- --------------------- There are no protocols associated with this patch. Security Keys Associated: ------------------------- Security Key Name ----------------- There are no security keys associated with this patch. Templates Associated: --------------------- Template Name Type File Name (Number) New/Modified/Deleted ------------- ------ ------------------ ----------------------- There are no templates associated with this patch. Additional Information: ----------------------- There is no additional information associated with this patch. New Service Requests (NSRs): ---------------------------- This project is initiated by Requirement BR 8.0 of the Health Information Exchange Viewer BRD #1-02-03-05-08-003. Patient Safety Issues (PSIs): ----------------------------- There are no patient safety issues associated with this patch. Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. Rational Defect 354112 Larger Studies Problem: Larger study is taking a long time to load the images Resolution: Image caching improvements made in this patch. Test results show acceptable load times. 2. Rational Defect 437547 Pan Function Problem: Pan functionality exhibited extensive lag and inadequate image adjustment with each user action. Resolution: Image caching improvements made in this patch. Test results show improved response when using pan functionality. 3. Rational Defect 437552 Hard to view PDF documents Problem: The zoom button is difficult to use. The experience improves with 'Fit to Window' option, but no scrolling is available to access the entire image area. Resolution: Scroll bar is added to improve viewing of .pdf documents 4. Rational Defect 464629 FPS notation Problem: Users see no reason for the FPS notation to exist when the study has no purpose for Cine. Resolution: Issue with FPS notation is fixed and the FPS notation no longer appears on studies where it has no purpose. 5. Rational Defect 464632 Progress Bar Problem: Progress bar is not close to accurate during the image loading process. The progress bar always ends partially done. Resolution: Defect open as a misinterpretation of the meaning of the user interface item which was deemed confusing and therefore removed. No impact to user functionality. 6. Rational Defect 464651 Window/Level Problem: The Window/Level function jerky at times. Resolution: Window/Level function improved. Testing confirmed acceptable performance. Test Sites: ------------ El Paso, TX Puget Sound, WA Kansas City, KS Documentation Retrieval Instructions: ===================================== See "Software and 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: 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: https://www4.domain.ext/vdl/ Title File Name FTP Mode ---------------------- ----------------------------------------- --------- MAG*3.0*177 KIDS MAG3_0P177.KID ASCII MAG*3.0*177 VIX Setup MAG3_0P177_VIX_Setup.msi Binary MAG*3.0*177 Patch MAG3_0P177_Patch_Description.pdf Binary Description MAG*3.0*177 VIX MAG3_0P177_VIX_Installaiton_Guide.pdf Binary Installation Guide VIX Admin Guide MAG_VIX_Admin_Guide.pdf Binary Patch Installation: =================== Pre/Post Installation Overview: ------------------------------- See readme file Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Imaging/Patches/MAG_3.0_177

Patch Subject: PMI MAPPING - FY18 #1 Description: ============ NOTE: This patch is part of NDF Data Update FY18 #1, which is comprised of two patches, PSN*4*536 and PSN*4*537. 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: ========================== N/A Test Sites: =========== Palo Alto HCS 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_537

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

Patch Subject: MID-FY19 CHANGES FOR 4 CHAR CDS NATIONAL CLINIC (#728.441) FILE Description: ============ Patch ECX*3.0*172 updates the SHORT DESCRIPTION (#1) field of nine existing entries in the NATIONAL CLINIC (#728.441) file. ************************************************************************* NOTE: This patch has a shortened compliance date because it must be installed as close to 4/1/2019 as possible. Sites will need the updates for Mid Fiscal Year (FY) 19. ************************************************************************* Patch Components: ----------------- Files & Fields Associated: N/A 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 Remote Procedures Associated: N/A Parameter Definitions Associated: N/A Additional Information: Blood Bank Team Coordination: ---------------------------- N/A New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC3191976 - MID-FY19 CHANGES FOR 4 CHAR CDS NATIONAL CLINIC (#728.441) FILE Problem: -------- A request was made by the Managerial Cost Accounting Office (MCAO) to update the SHORT DESCRIPTION (#1) field of nine existing entries in the NATIONAL CLINIC (#728.441) file. Resolution: ----------- Routine ECX3P172 has been created to update the NATIONAL CLINIC (#728.441) file by modifying the SHORT DESCRIPTION (#1) field of nine existing entries effective 4/1/2019. The descriptions of the following entries have changed: Existing Code New Short Description --------------- ------------------------- CNSI SCI/D Telehealth HTSC VHA DECLARED DISASTER RESPONSE HTUC CHAR4 COUNCIL HTVC HT Program Video Visit POPP CHAR4 COUNCIL RHGC Chiropractic SCHC EVP Whole Health SCVT EVP ACT SNVC EVP Mindful Movement Test Sites: ---------- VA Heartland (STL, POP, MRN) Central Plains (OMA, DES, IOW) Software and Documentation Retrieval Instructions: ---------------------------------------------------- N/A Patch Installation: Pre/Post Installation Overview: ------------------------------- You may install this patch at any time without interruption to users. It should take less than 2 minutes to install this patch. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/DSS+Extracts/Patches/ECX_3.0_172

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

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

Patch Subject: MAP SUMMARY DOCUMENT ARCHITECTURE Description: ============ This patch provides an option to map a VistA resource to a representation of a Summary Document Architecture (SDA) data type. The patch includes a new ENTITY (#1.5) file. The ENTITY file defines the VistA resource being mapped to an SDA type. Patch Components: ----------------- File Name (#) Field Name (#) New/Modified/Deleted ------------- -------------- ------------- Entity (#1.5) New Form Name File # New/Modified/Deleted --------- ------ -------------------- DDE ENTITY ENTER/EDIT 1.5 New Option Name Type New/Modified/Deleted ----------- ---- -------------------- Entity Enter/Edit [DDE ENTITY ENTER/EDIT] run routine New Entity Mapping [DDE ENTITY MAPPING] menu New Other Options[DIOTHER] menu Modified Input Template File # New/Modified/Deleted -------------- ------ -------------------- DDE EDIT ENITY 1.5 New Blood Bank Clearance: --------------------- EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch DI*22.2*9 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*9 have no effect on Blood Bank software functionality, therefore RISK's none. Test Sites: ----------- Charleston, SC North Chicago, IL Software and Documentation Retrieval Instructions: -------------------------------------------------- Software is being released as a host file and 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: Hines: domain.ext Salt Lake City: domain.ext Software File Name SFTP Mode ------------------------------------------------------------------ VPR*1*8 & DI*22.2*9 DI_222_9_VPR_1_8.KID ASCII 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 Technical Manual FM22_2TM.PDF Binary Patch Installation: ------------------- Software is being released as a host file, DI_222_9_VPR_1_8.KID. The host file contains two patches; DI*22.2*9 and VPR*1*8. Patches DI*22.2*9 and VPR*1*8 are scheduled to be released nationally as a bundle. Installation of these patches into Production within the first 15 days from the National Release date is requested. The VA leadership has asked for an expedited release to comply with the schedule for the high profile Mission Act. Certain functionality has to be loaded into production in 130 VA Medical Centers within a short timeframe. We appreciate your cooperation. Use default answers for KIDS load/install questions. Multi-Build: http://code.osehra.org/VistA.git/blob/master/Packages/MultiBuilds/DI_222_9_VPR_1_8.KIDs Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Virtual+Patient+Record/Patches/VPR_1.0_8

Patch Subject: EPIP CONTROLLED SUBSTANCES REMEDIATION 2.0 Description: ============ ------------ Patch PSD*3.0*87 corrects an issue with the BALANCE DISCREPANCY CHECK prompt, as reported by a VA site after the release of PSD*3.0*84. The issue is that when the PRIME VENDOR field (#12) is set to NO or null, the BALANCE DISCREPANCY CHECK prompt does not appear as expected when using the Create/Edit the Narcotic Area of Use [PSD NAOU EDIT] option. The routine PSDEN is modified to always display the BALANCE DISCREPANCY CHECK prompt whether the PRIME VENDOR field is set to YES or NO. 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 Parameters Associated: Parameter 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: -------------------------------------------- INC3380754 - BALANCE DISCREPANCY CHECK prompt not displaying when PRIME VENDOR field is null or set to No Problem: ------- If the PRIME VENDOR field (#12) is null or set to No, then the BALANCE DISCREPANCY CHECK prompt will not show to the user. Resolution: ---------- This patch for a patch is created in support of PSD*3.0*84. PSD*3.0*84 added the BALANCE DISCREPANCY CHECK field (#37) to the DRUG ACCOUNTABILITY STATS file (#58.8). Routine PSDEN is used to display fields from this file for editing when the LOCATION TYPE field (#1) is set to "MASTER VAULT." After release of PSD*3.0*84, it was discovered that if the PRIME VENDOR field (#12) is set to NO or null, then the BALANCE DISCREPANCY CHECK prompt will not display as expected. Patch PSD*3.0*87 allows the BALANCE DISCREPANCY CHECK field to be edited regardless of the state of the PRIME VENDOR field, while maintaining the original branching flow connected to the PRIME VENDOR field. Test Sites: ---------- Milwaukee VA Medical Center, Milwaukee, WI Fargo VA Health Care System, Fargo, ND Software and Documentation Retrieval Instructions: --------------------------------------------------- The software is released as a PackMan patch message and is distributed from FORUM. There are no VA Software Document Library (VDL) manuals associated with this patch release. Patch Installation: Pre/Post Installation Overview: ------------------------------- Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Controlled+Substances/Patches/PSD_3.0_87

Patch Subject: CANCELLED TO DISCONTINUED CONSULTS Description: ============ This patch contains a new routine that does the following: 1. An overnight TaskMan job called GMRC CHANGE STATUS X TO DC will run for a period of time specified by a new parameter called CSLT CANCELLED TO DISCONTINUED. Following the installation of this patch, that period of time will be 31 days prior to today, and going back in time to 365 days prior to today. **NOTE: The GMRC CHANGE STATUS X TO DC option should never be run from any menu. If that were attempted, the user will receive a message "This option is only for use by TaskMan as an overnight job"** 2. The overnight job will find consults that were cancelled in the period defined in 1. above, and will discontinue those consults. 3. A new option called GMRC CX TO DC PARAMETER EDIT will be installed by the patch. This option will allow users at VA sites to change the timescale referred to in 1. above. 4. The patch will install an option in file #19.2 (OPTION SCHEDULING) called GMRC CHANGE STATUS X TO DC. It will initially be set to run at 11:00 PM every night. 5. A temporary file in the XTMP namespace will be created during the overnight job. This file will contain details of every consult that was discontinued. The file will be set to be purged after 60 days. Patch Components ================ Files & Fields Associated: New/Modified/ File Name (Number) Field Name(Number) Deleted ------------------- ------------------ ------------- REQUEST/CONSULTATION (#123) REQUEST PROCESSING ACTIVITY (#40),sub-fields .01 (DATE/TIME OF ACTION) and #1 (ACTIVITY) Modified,new index "ASTATUS" Forms Associated: New/Modified/ Form Name File Number Deleted --------- ----------- ------------- N/A Mail Groups Associated: New/Modified/ Mail Group Name Deleted --------------- ------------- N/A Options Associated: New/Modified/ Option Name Type Deleted ----------- ---- ------------- GMRC CHANGE STATUS X TO DC Run Routine New GMRC CX TO DC PARAMETER EDIT Run Routine New Protocols Associated: New/Modified/ Protocol Name Deleted ------------- ------------- N/A Security Keys Associated: New/Modified/ Security Key Name Deleted ----------------- ------------- N/A Templates Associated: New/Modified/ Template Name Type File Name (Number) Deleted ------------- ---- ------------------ ------------- N/A Additional Information: ----------------------- N/A New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- N/A Test Sites: ---------- Houston Salisbury Software and Documentation Retrieval Instructions: -------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www.domain.ext/vdl/ Title File Name FTP Mode ----------------------------------------------------------------------- Consult/Request Technical Manual constm.pdf Binary Consult/Request Technical Manual constm.doc Binary Consult/Request Tracking User Manual consum.pdf Binary Consult/Request Tracking User Manual consum.docx Binary Patch Installation: ***************************************** DO NOT QUEUE the install of this patch. ***************************************** Pre/Post Installation Overview ------------------------------ Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Consult+Request+Tracking/Patches/GMRC_3.0_113

Patch Subject: MCCF EDI TAS EBILLING BUILD 5/6 Description: ============ Integrated Billing (IB) is a software module within Veterans Health Information Systems and Technology Architecture (VistA) that provides the ability for billing personnel to submit claims in either a paper or electronic format to third-party payers. The following features of the IB software will be affected by this patch: * Transmitting SNF Claims with Appropriate Revenue Codes The IB VistA package has been modified to send Revenue Code 0022 and VA specific AAA00 RUG/Health Insurance Prospective Payment System (HIPPS) Skilled Nursing Facility (SNF) rate codes for Medicare Primary Institutional Part A claims with bill types 21x, 22x or 23x. Due to this modification, the System will no longer use the Financial Service Center (FSC) workaround. Instead, the System now has the ability to perform the identical checks that FSC used to ensure that these SNF claims are sent. The System automatically allows for this in the transmission of the flat file so that the biller does not have to enter anything additional to have this information transmitted. In addition, the VistA flat file for Institutional 837s has been updated and the "View/Print EDI Bill Extract Data" [IBCE EDI VIEW/PRINT EXTRACT] (VPE) option screens depict the change in the flat file for the end user to view in the INS segment. * Add 'T' for Transmitted to RCB Screen The IB VistA package has been modified to be enable the user to see "** T = Test Claim" (to explain what the "T" indicator represents) in the legend of the "View/Resubmit Claims - Live or Test" [IBCE PREV TRANSMITTED CLAIMS] (RCB) option screen when viewing previously Printed claims. * Remove Ability to Define Insurance Company as non-EDI The IB VistA package has been modified so the "Insurance Company Entry/Edit" [IBCN INSURANCE CO EDIT] (EI) option no longer provides the user the ability to select "0 - NO" as an option for "EDI - Transmit?" prompt under the EDI Parameters section of the screen. In addition, a one-time report from each site showing the value of the field to determine whether an Insurance Company is active for Electronic Data Interchange (EDI) will be sent to the eBiz Rapid Response group. * RCB Screen - Match COB Data to Payer Sequence The IB VistA package has been modified to be enable the user to resubmit, to the Test queue, a claim using the "View/Resubmit Claims - Live or Test" [IBCE PREV TRANSMITTED CLAIMS] (RCB) option and have only the Coordination of Benefits (COB) data that is correct for the payer sequence be included in the transaction. If a user selects: o a Primary claim to resubmit and the claim has received an EOB/MRA from the primary payer, VistA will not send the COB data from the EOB/MRA and the amount billed will not be offset by previous payments from the primary payer. o a Secondary claim to resubmit and the claim has received an EOB/MRA from the secondary payer, VistA will not send the COB data from the EOB/MRA and the amount billed will not be offset by previous payments from the secondary payer. o a Tertiary claim to resubmit and the claim has received an EOB/MRA from the tertiary payer, VistA will not send the COB data from the EOB/MRA and the amount billed will not be offset by previous payments from the tertiary payer. If a user attempts to resubmit a claim(s) with EOB data in VistA to the Production queue, the system will filter out the claim(s) and not transmit it. These non-transmitted claims will be listed on the screen as "Skipped". * Non-MCCF Unbilled Amounts Report The IB VistA package has been modified so the "Re-Generate Unbilled Amounts Report" [IBT RE-GEN UNBILLED REPORT] option now allows the user to select the following additional search criteria: (M)CCF, (N)on-MCCF (Outpatient Only), or (B)oth claims Non-MCCF Rate Types include: CHAMPVA, CHAMPVA Reimb. Ins., TRICARE, TRICARE Reimb. Ins., Interagency, Sharing Agreement and Ineligible. Non-MCCF Appointment Types include: Employee and Sharing Agreement. Non-MCCF Eligibility of Encounters include: CHAMPVA, TRICARE, Employee, Ineligible and Sharing Agreement. * Non-MCCF Pay-To Address Rate Types The IB VistA package has been modified to allow the user to be able to define one or more Rate Types for which the non-MCCF Pay-to Address (formerly the TRICARE Pay-to Address) will be used on claims with one of those Rate Types. In addition, the following items are capable: o An authorized user with access to the IB Site Parameters and the TRICARE Pay-to security key will be able to add/delete a Rate Type for which claims with that Rate Type will use the non-MCCF Pay-to Address data. o The System will use the non-MCCF Pay-to Address data on claims with specified Rate Types only when the non-MCCF Pay-to Address is not exactly the same as the Billing Provider Name and Address. o The System will transmit the TRICARE Pay-to Address data on claims with specified Rate Types in the 837-I, 837-P or 837-D when the non-MCCF Pay-to Address is not exactly the same as the Billing Provider Name and Address. o The System will print the non-MCCF Pay-to Address data on Institutional claims with specified Rate Types on the UB04 form (FL2) when the TRICARE Pay-to Address is not exactly the same as the Billing Provider Name and Address. o The System will print the non-MCCF Pay-to Address data on Professional claims with specified Rate Types on the CMS 1500 form (Box 33) when the non-MCCF Pay-to Address is not exactly the same as the Billing Provider Name and Address. * Remove Fatal Error - Rendering Provider CMS 1500 The IB VistA package has been modified so that the previously fatal error that prevented a biller from submitting a Professional Claim with no Rendering Provider has been removed and instead now a non-fatal warning message appears to the user when a Professional Claim does not contain a Rendering Provider. * CMN Oxygen and EPN Nutrition The IB VistA package has been modified to enable the "Enter/Edit Billing Information" [IB EDIT BILLING INFO] option to enter the required data for an Oxygen Certificate of Medical Necessity (CMN) (CMS-484.3) or an Enteral and Parenteral Nutrition CMN (CMS-10126) when completing a professional bill for Durable Medical Equipment (DME). In addition, the ability to transmit Professional claims has been modified to include the CMN data in the proprietary 837-P Transaction to the Financial Services Center (FSC). Patch Components ================ Files & Fields Associated: File Name (#) New/Modified/ Sub-file Name (#) Field Name (Number) Deleted ------------------- --------------------------------- ------------- INSURANCE COMPANY (#36) Modified TRANSMIT ELECTRONICALLY (#3.01) Modified IB ERROR (#350.8) Data Only Screen: I $$INCLUDE^IBY608PR(8,Y) IB SITE PARAMETERS (#350.9) Modified CMN CPT CODES sub-file (#350.916) New NON-MCCF RATE TYPES FOR PTP sub-file (#350.928) New TRICARE PAY-TO PROVIDERS sub-file (#350.929) Modified TC FACILITY (#.01) Modified TC NAME (#.02) Modified TC FEDERAL TAX NUMBER (#.03) Modified TC TELEPHONE NUMBER (#.04) Modified TC PARENT PAY-TO PROVIDER (#.05) Modified TC STREET ADDRESS 1 (#1.01) Modified TC STREET ADDRESS 2 (#1.02) Modified TC CITY (#1.03) Modified TC STATE (#1.04) Modified TC ZIP (#1.05) Modified IB DATA ELEMENT DEFINITION (#364.5) Data Only Screen: I $$INCLUDE^IBY608PR(5,Y) IB FORM SKELETON DEFINITION (#364.6) Data Only Screen: I $$INCLUDE^IBY608PR(6,Y) IB FORM FIELD CONTENT (#364.7) Data Only Screen: I $$INCLUDE^IBY608PR(7,Y) BILL/CLAIMS (#399) Modified PROCEDURES sub-file (#399.0304) Modified CMN REQUIRED? (#23) New CMN FORM TYPE (#24) New CMN CERTIFICATION TYPE (#24.01) New CMN PATIENT HEIGHT (IN) (#24.02) New CMN PATIENT WEIGHT (LBS) (#24.03) New CMN MONTHS DME EQUIP NEEDED New (#24.04) CMN DATE THERAPY STARTED (#24.05) New CMN LAST CERTIFICATION DATE New (#24.06) CMN RECERTIFICATION/REVISN DT New (#24.07) CMN REPLACEMENT ITEM? (#24.08) New CMN ABG PO2 (MMHG) (#24.1) New CMN O2 SATURATION % (#24.102) New CMN DT LAST ABG PO2 AND O2 SAT New (#24.103) CMN EDEMA DUE TO CHF PRESENT? New (#24.104) CMN COR PULMONARY HYPERTENSN? New (#24.105) CMN HEMATOCRIT > 56%? (#24.106) New CMN PT CONDITION AT TEST TIME New (#24.107) CMN TEST CONDITIONS (#24.108) New CMN PORTABLE O2 INDICATOR (#24.109) New CMN HIGHEST O2 FLOW RATE (#24.11) New CMN LAST 4 LPM ABG PO2 (MMHG) New (#24.111) CMN LAST 4 LPM O2 SATURATION % New (#24.113) CMN DATE OF LAST 4 LPM TESTS New (#24.114) CMN EQUIPMENT/COST DESCRIPTION New (#24.115) CMN SM BOWEL ABSORPTION DOC? New (#24.201) CMN ENTERAL NUTRITION BY TUBE? New (#24.202) CMN PROCEDURE A CALORIES (#24.203) New CMN PROCEDURE A (#24.204) New CMN METHOD OF ADMINISTRATION New (#24.205) CMN DAYS PER WEEK ADMINISTERED New (#24.206) CMN SEVERE MALABSORPTION DOC? New (#24.207) CMN AMINO ACID (ML/DAY) (#24.208) New CMN AMINO ACID CONCENTRATION % New (#24.209) CMN AMINO ACID PROTEIN (GM/DY) New (#24.21) CMN DEXTROSE (ML/DAY) (#24.211) New CMN DEXTROSE CONCENTRATION % New (#24.212) CMN LIPIDS (ML/DAY) (#24.213) New CMN ROUTE OF ADMINISTRATION New (#24.214) CMN LIPIDS (DAYS/WEEK) (#24.215) New CMN LIPIDS CONCENTRATE % (#24.216) New CMN PARENTERAL/ENTERAL/BOTH New (#24.217) CMN PROCEDURE B CALORIES (#24.218) New CMN PROCEDURE B (#24.219) New CMN FORM TYPES (#399.6) New Bulletins Associated: New/Modified/ Bulletin Name Deleted ------------- ------------- N/A Dialogs Associated: New/Modified/ Dialog Name Deleted ----------- ------------- N/A Forms Associated: New/Modified/ Form Name File Name (Number) Deleted --------- ------------------ ------------- N/A Functions Associated: New/Modified/ Function Name Deleted ------------- ------------- N/A HL Logical Link: New/Modified/ HL Logical Name Deleted --------------- ------------- N/A HL7 Application Parameters: New/Modified/ HL7 Parameter Name Deleted ------------------ ------------- N/A HLO Application Registry: New/Modified/ HLO Registry Name Deleted ----------------- ------------- N/A Help Frames Associated: New/Modified/ Help Frame Name Deleted --------------- ------------- N/A Mail Groups Associated: New/Modified/ Mail Group Name Deleted --------------- ------------- N/A Options Associated: 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 ------------- ------------- IBJP IB NON-MCCF PAY-TO PROVIDERS MENU New IBJP IB NON-MCCF RATE TYPE ADD New IBJP IB NON-MCCF RATE TYPE DEL New IBJP IB NON-MCCF RATE TYPES New IBJP IB NON-MCCF RATE TYPES MENU New IBJP IB TRICARE PAY-TO PROVIDER ADD Modified IBJP IB TRICARE PAY-TO PROVIDER DEL Modified IBJP IB TRICARE PAY-TO PROVIDER DIVISIONS Modified IBJP IB TRICARE PAY-TO PROVIDER EDIT Modified IBJP IB TRICARE PAY-TO PROVIDERS MENU Deleted IBJPS CMN CPT ADD New IBJPS CMN CPT DEL New IBJPS CMN CPT MENU New 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 ------------- ---- ------------------ ------------- IBEDIT INS CO1 Input INSURANCE COMPANY (#36) Modified Templates, List Associated: New/Modified/ Template Name Type Deleted ------------- ---- ------------- IBJP IB NON-MCCF List New RATE TYPES IBJP IB TRICARE List Modified PAY-TO PROVS IBJPS CMN CPTS List New Templates, Print Associated: New/Modified/ Template Name Type File Name (Number) Deleted ------------- ---- ------------------ ------------- N/A Templates, Sort Associated: New/Modified/ Template Name Type File Name (Number) Deleted ------------- ---- ------------------ ------------- N/A New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A Defect Tracking System Ticket(s) & Overview ------------------------------------------- 1. INC4006791 - The option to add a Dental Payer ID and address in the Insurance Company Editor is missing. This is a VA wide issue. Problem: ------- The option to add a Dental Payer ID and address in the Insurance Company Entry/Edit [IBCN INSURANCE CO EDIT] is missing. This is a VA wide issue. Resolution: ---------- Insurance Company Entry/Edit [IBCN INSURANCE CO EDIT] which was enhanced in IB*2.0*592 to support the addition of electronic dental claims, EDI X12 837D, was overwritten in error in a subsequent patch and is being restored in order to prompt users for Dental Payer ID and address. Test Sites: ---------- Dublin Martinsburg Orlando Tomah 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: Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/ Title File Name FTP Mode ----------------------------------------------------------------------- Deployment, Installation, ib_2_0_p608_ig.pdf Binary Back-out/Rollback Guide (IB*2.0*608) EDI User Guide ib_2_0_p608_edi_ug.pdf Binary Integrated Billing (IB) V.2.0 ib_2_0_p608_tm.pdf Binary Technical Manual Patch Installation: Pre/Post Installation Overview ------------------------------ Of note, included in this patch is a modification to line 2 in the routine IBCU7 to correct the patch sequencing that was entered as part of the IB*2.0*592 patch. This change has no effect on the functionality of the routine and was only made to correct the patch sequencing of line 2. ************************************************************************* * IMPORTANT NOTE * * In PRODUCTION, there is one **MANDATORY** pre-installation activity * * associated with this install. * * * * The IB Staff MUST empty the 837 extract/transmission queue PRIOR to * * the installation of this patch. * ************************************************************************* INSTRUCTIONS ON HOW TO EMPTY THE 837 EXTRACT TRANSMISSION QUEUE: =============================================================== The site Information Resource Management (IRM) MUST coordinate with the Billing Department to ensure that the 837 extract/transmission queue is empty. Once the Billing Department has completed the instructions, the Billing department is to inform IRM that the patch installation may proceed. The instructions to empty the queue are as follows: Select the option: TRANSMIT EDI BILLS - MANUAL [IBCE 837 MANUAL TRANSMIT] What is the purpose of this option? This option is used to by-pass the normal daily/nightly transmission queues if the need arises to get the claim to the payer quickly. When is this option used? There are occasions when there is a need to transmit a claim(s) immediately instead of waiting for the batching frequency as scheduled in the MCCR Site Parameter. This option will allow sending individual claim(s) or all claims in a ready for extract status. Upon selecting this option, you will be prompted with the following: Select one of the following: A Transmit (A)LL bills in READY FOR EXTRACT status S Transmit only (S)ELECTED bills You should select 'A' for ALL There are no other mandatory pre-installation activities associated with this patch. ------------------------------------------------------------------------ The Pre-install routine (IBY608PR) will automatically do the following: * Add/Update entries used by the Forms Output Utility [IBCE OUTPUT FORMATTER]. * Add new entries in IB ERROR file (#350.8). The Post-install routine (IBY608PO) will automatically generate the one- time Insurance Company EDI Parameter Report and send an email to the eBiz Rapid Response Group ("[email protected]"). This report will list all of the insurance companies that have the current setting for the Transmit Electronically parameter set to ZERO which equals 'NO'. In addition, the Post-install routine will automatically add 50 CPT codes to the new CMN CPT CODE INCLUSION IB Site Parameter. This list of codes is a basis of those CPT codes to be referenced in processing claims which contain CMN Oxygen EPN Nutrition data. This list of CPT codes can be maintained when accessing the IB Site Parameters. Routines IBY608PO and IBY608PR may be manually deleted by IT/IRM upon completion of 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_608

Patch Subject: HEALTHSHARE FIXES Description: ============ This patch to the Virtual Patient Record (VPR) application updates VPR entries in the Entity file (#1.5) to correct 6 issues with the HealthShare (HS) interface that were identified too late to be addressed in VPR*1*8: 1. Problems merged --------------- If the same problem is entered for a patient at multiple VA facilities, HS will attempt to merge those entries in its Edge Cache Repository (ECR). This patch adds the ExternalId property to the Problem container Entities to prevent HS from attempting this merge. 2. Allergies merged ---------------- Like with problems, HS will attempt to merge the same allergy entered for a patient at multiple VA facilities in its ECR. This patch adds the ExternalId property to the Allergy container Entities to prevent HS from attempting this merge. 3. Radiology exam sets missing reports ----------------------------------- The RadOrder container in HS only provides a link to a single report as the result of an order; if an exam set is registered, multiple reports may be created. This patch adds the DocumentNumbers property to the RadOrder extension Entity to hold all report identifiers for an order. 4. Incorrect LOINC codes for Pathology reports ------------------------------------------- A general LOINC code was previously assigned to all pathology reports when stored in HS, for ease of searching; this patch changes the Anatomic Pathology Entities for the Document container to now assign a code based on the VistA Lab section. 5. Missing Pathology orders ------------------------ Previously only Chemistry orders were included in the LabOrder container, resulting in incomplete lab data for a patient and difficulty navigating to the pathology reports in SDA. All Lab orders will now be returned. 6. Unknown Last Date of Treatment ------------------------------ HS has the ability to aggregate data for a patient from multiple VA facilities, but cannot easily identify which site treated the patient most recently. This patch adds the LastTreated property to the VPR PATIENT EXTENSION entity to store the date of the last visit for each patient at a given VA facility. Patch Components: ----------------- Entities Associated: Entity Name New/Modified/Deleted ----------- -------------------- VPR ALLERGY Modified VPR ALLERGY ASSESSMENT Modified VPR FIM Modified VPR LAB ORDER Modified VPR LOCATION EXTENSION Modified VPR LR RESULT EXTENSION Modified VPR LRAP EXTENSION Modified VPR LRAP REPORT Modified VPR LRCH RESULT Modified VPR LRCY RESULT Modified VPR LREM RESULT Modified VPR LRMI EXTENSION Modified VPR LRMI REPORT Modified VPR LRMI RESULT Modified VPR LRSP RESULT Modified VPR MEDICATION Modified VPR OTHER ORDER Modified VPR PATIENT Modified VPR PATIENT EXTENSION Modified VPR PATIENT ID Modified VPR PROBLEM Modified VPR RAD ORDER Modified VPR RAD REPORT Modified VPR RAD RESULT Modified VPR RAD RESULT EXTENSION Modified VPR RAD RPT EXTENSION Modified VPR SOURCE FACILITY New Files & Fields Associated: N/A Forms Associated: N/A Mail Groups Associated: N/A Options Associated: N/A Protocols Associated: N/A Remote Procedure Calls Associated: N/A Security Keys Associated: N/A Templates Associated: N/A Blood Bank Team Coordination: N/A New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- N/A Test Sites: ----------- Charleston, SC North Chicago, IL Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released as a KIDS build. Patch Installation: Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Virtual+Patient+Record/Patches/VPR_1.0_10

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

Patch Subject: VIXImage Viewer 2.01 Description: ============ Associated Patches: MAG*3.0*185 KIDS must be installed before installing MAG*3.0*197 KIDS Subject: VIX IMAGE VIEWER VERSION 2.01 Category: ROUTINE Description: --------------- This document describes MAG*3.0*197, the VIX Image Viewer 2.01 patch. This patch adds enhancements to the Zero footprint HTML 5 based image viewer. Major changes for this patch are summarized below. MAG*3.0*197 contains the following new features: - Support for MUSE EKGs - HTML 5 optimizations - SQL optimization - Updates to SQL Express 2017 (Addresses issues found with Nessus scan) - Cache image files from remote locations only - Ability to copy an image to the clipboard - Fortify remediations - Newly supported SOP classes in MAG*3.0*197, as indicated in this document Patch Components: ----------------------- This patch includes the following files: File Name............................... Description.................... MAG3_0P197.KID KIDS (Kernel Installation & Distribution System) package to be installed on the VistA System. MAG3_0P197_VIX_Setup.msi Installation file for the VIX software. MAG3_0P197_Patch_Description_Document.pdf This document MAG3_0P197_VIX_Installation_Guide.pdf VIX Installation Guide for this patch. MAG3_0P197_User_Guide.pdf User Guide for this patch. SQLExpress_x64-14.0.1000.169.zip 2017 SQL Express zip file MAG3_0P197_README.txt MAG*3.0*197 Readme SSMS-Setup-ENU.exe SQL Server Management Studio 17.4 This patch installs the following versions: Apache Tomcat: 8.0.45 Java: 1.80_121 2017 SQL Express (.zip file) Documentation: This document provides an overview, explains the changes, and outlines the installation for this patch. Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ----------------------- ------------------- -------------------- There are no files or fields associated with this patch. Forms Associated: Form Name File # New/Modified/Deleted -------------- -------- -------------------- There are no forms associated with this patch. Mail Groups Associated: Mail Group Name New/Modified/Deleted ---------------------- --------------------------- There are no mail groups associated with this patch. Options Associated: Option Name Type New/Modified/Deleted ----------------- ------ -------------------- There are no options associated with this patch. Protocols Associated: Protocol Name New/Modified/Deleted ------------------ --------------------------- There are no protocols associated with this patch. Security Keys Associated: Security Key Name ----------------- There are no security keys associated with this patch. Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- There are no templates associated with this patch. Additional Information: There is no additional information associated with this patch. New Service Requests (NSRs): ------------------------------------- This project is initiated by Requirement BR 8.0 of the Health Information Exchange Viewer BRD #1-02-03-05-08-003. Patient Safety Issues (PSIs): ---------------------------------- There are no patient safety issues associated with this patch. Supported SOP Classes --------------------------- The following table includes the newly supported SOP classes in MAG*3.0*197. The HDIG validates the objects associated with these classes and stores them in the new database that then can be viewed via the new Image Viewer. Each SOP class must be enabled individually to be stored. The patch is distributed with all SOP classes disabled as the default. To enable the storage of new SOP classes, please enter a ServiceNow ticket, or contact the National Help Desk to request assistance from the CLIN3 Support Team. NOTE: Newly Supported SOP Classes are not currently viewable with Clinical Display or VistA RAD. SOP Classes Newly Supported in MAG*3.0*197: SOP Class Name SOP Class UID ---------------- ----------------------------- Mammography CAD SR 1.2.840.10008.5.1.4.1.1.88.50 3D Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.13.1.1 MR Image Storage 1.2.840.10008.5.1.4.1.1.4 Defect Tracking System Ticket(s) & Overview: ------------------------------------------- 1. Rational Defect 538648: Confirmed Image Compression NOT working at all for the Image Viewer. Problem: ------------ The Image Viewer was configured and tested for both compressed and uncompressed images and the results were compared side by side. Compression configuration for Image Viewer was confirmed NOT working. Image files are the same size no matter if compression is enabled or disabled. The image files are of full size in both cases. Resolution: -------------- Compressed file sizes confirmed image compression is working. 2. Rational Defect 711568: Several sites that have installed P185 on their VIX are reporting that Importer III stopped working. Problem: ---------- The Importer III is failing after installing P185 on VIX. Resolution: ------------- The 197 KIDS file will be updated to include registration of the RPC 'MAGVA GET ALL NETWORK LOCATIONS', also instructions provided in MAG3_0P197_README.TXT to address the Network Location entries w/o a Place field value. Test Sites: ------------- Heartland East, MO Las Vegas, NV Hampton, VA Pittsburgh, PA Software and Documentation Retrieval Instructions: -------------------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS software directory at the following OI Field Offices: Hines domain.ext Salt Lake City domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ Title File Name FTP Mode ---------------------------------------------------------------------------------- MAG*3.0*197 KIDS MAG3_0P197.KID ASCII MAG*3.0*197 VIX Setup MAG3_0P197_VIX_Setup.msi Binary MAG*3.0*197 Patch MAG3_0P197_Patch Description Binary Description _Document.pdf MAG*3.0*197 VIX MAG3_0P197_VIX_Installation_ Binary Installation Guide Guide.pdf 2017 SQL Express ZIP SQLExpress_x64-14.0.1000.169.zip Binary File MAG*3.0*197 Readme MAG3_0P197_README.txt Binary *SQL Server Management SSMS-Setup-ENU.exe Binary Studio 17.4 * Download of this file is optional. SQL Server Management Studio is intended for debugging purposes if needed. Sites may wish to defer downloading this very large file until actual need for it in the future. Patch Installation: Pre/Post Installation Overview: --------------------------------------- See MAG*3.0*197 VIX Installation Guide for additional information. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages

Patch Subject: VIX IMAGE VIEWER VERSION 3.0 Description: ============ MAG*3.0*201 adds enhancements to the Zero footprint HTML 5 based image viewer. MAG*3.0*201 contains the following new features: 1) Global annotation settings of images a. User annotation preferences b. View annotation audit history (user, time, etc.) 2) Annotate DICOM images 3) Release of Information (ROI) patient's images or studies or report document. a. Viewer patient ROI submission and processing b. Monitor ROI submitted print queue status Note 1: If you are upgrading from P177 VIX to P201 VIX on the site VIX server, or don't have SQL2017 Express installed currently then you must remove the old (retired) SQL2014 features first by hand before running the P201 VIX Setup Wizard. See details in the MAG3_0P201_VIX_INSTALLATION_GUIDE.pdf Note 2: Also please follow P197 README file (see detailed instructions in MAG3_0P197_README) regarding confirming Tomcat User permissions, disabling archive scanning in McAfee and checking for Network locations without a place value. Patch Components: ----------------- This patch includes the following files: File Name Description --------- ----------- MAG3_0P201.KID KIDS (Kernel Installation & Distribution System) package to be installed on the VistA System MAG3_0P201_VIX_Setup.msi Installation file for the VIX(30.201.9.6250) software. MAG3_0P201_Patch_ Description_Document.pdf This document MAG3_0P201_VIX_Installation _Guide.pdf VIX Installation Guide for this patch. VIX Software - MAG3_0P201_VIX_Setup.msi(30.201.9.6250) If this is a new install or an upgrade, this patch installs the following versions: . Apache Tomcat: 8.0.52 . Java: 1.80_171 Documentation: This document provides an overview, explains the changes, and outlines the installation for this patch. 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 ----------- ---- -------------------- Delete work items run routine New [MAG WORK ITEMS DELETE] (For the site to purge old/non-processed work item, e.g.: PRECACHE, IMPORTER, ROI. etc.) For example: (from VistA menu option) Delete out-date ROI request from WORK ITEM Select OPTION NAME: MAG WORK ITEMS DELETE Delete work items Delete work items Enter from date: T-300 (DEC 28, 2017) Enter through date: T (OCT 24, 2018) Select work item type: ? Answer with WORKLIST NAME Choose from: IMPORTER PRECACHE ROI StorageCommit Enter a work item type. Select work item type: ROI Select work item subtype: ? Answer with MAG WORK ITEM SUBTYPE NAME Choose from: ACQUISITION DicomCorrect DirectImport NetworkImport Process REGISTRATION REMOTEPRIOR StagedMedia StorageCommit Enter a work item subtype. Select work item subtype: Process ARE YOU SURE YOU WANT TO DELETE WORK ITEMS? NO// YES Protocols Associated: Protocol Name New/Modified/Deleted ------------------ --------------------------- MAG PRECACHE 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): ---------------------------- This project is initiated by Requirement BR 8.0 of the Health Information Exchange Viewer BRD #1-02-03-05-08-003. Patient Safety Issues (PSIs): ----------------------------- N/A Supported SOP Classes ---------------------- The following table includes the newly supported DICOM SOP classes in MAG*3.0*201. The Hybrid DICOM Image Gateway (HDIG) validates the objects associated with these classes and stores them in the new database that then can be viewed via the new Image Viewer. Each SOP class must be enabled individually to be stored. The patch is distributed with all SOP classes disabled as the default. To enable the storage of new SOP classes, please enter a ServiceNow ticket, or contact the National Help Desk to request assistance from the CLIN3 Support Team. NOTE: Newly Supported SOP Classes are not currently viewable with Clinical Display or VistARad. SOP Classes Newly Supported in MAG*3.0*201 SOP Class Name SOP Class UID ----------------------------- ------------- Positron Emission Tomography Image Storage 1.2.840.10008.5.1.4.1.1.128 Digital X-Ray Image Storage - For Presentation 1.2.840.10008.5.1.4.1.1.1.1 Defect Tracking System Ticket(s) & Overview: ------------------------------------------- 1. Rational Defect 694765: Provide the ability to save user annotation preferences Problem ---------- Users were not able to save user annotation preferences. Resolution ------------- The code was updated to allow user annotation in the New Image Viewer. Test Sites: ------------- Heartland West, MO Puget Sound, WA Software and Documentation Retrieval Instructions: -------------------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS software directory at the following OI Field Offices: Hines domain.ext Salt Lake City domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ Title File Name FTP Mode ----------------------------------------------------------------------------------- MAG*3.0*201 KIDS MAG3_0P201.KID ASCII MAG*3.0*201 VIX Setup MAG3_0P201_VIX_Setup.msi Binary MAG*3.0*201 Patch MAG3_0P201_Patch_Description_Document.pdf Binary Description MAG*3.0*201 VIX Guide MAG3_0P201_VIX_Installation_Guide.pdf Binary Patch Installation: Pre/Post Installation Overview: --------------------------------------- See MAG*3.0*201 VIX Installation Guide for additional information. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages

Patch Subject: VIX IMAGE VIEWER VERSION 3.2 Description: ============ MAG*3.0*221 adds enhancements to the Zero footprint HTML 5 based image viewer. MAG*3.0*221 contains the following new features: 1) Image Quality Assurance (QA) . Apply advance QA filters . Perform QA . Run QA report 2) Release of Information (ROI) . Process ROI request 3) Additional SOP Class Support **NOTE 1** There is a Post Installation Step that needs to be completed. The menu option Delete work items [MAG WORK ITEMS DELETE] must be run IMMEDIATELY AFTER the installation of the MAG*3.0*221 KIDs and BEFORE the installation of the VIX.msi. **NOTE 2** ROI functionality impaired by IE11 structure that sites cannot change. There is a tested fix that did not make this patch that does allow sites to download physical document ROI release. The fix will be held for a future patch. Meanwhile, ROI functionality remains in VistA Imaging Display and can be utilized. Patch Components: ----------------- This patch includes the following files. MAG3_0P221_README.txt, if present, is an informative file associated with the patch released: File Name Description --------- ------------ MAG3_0P221.KID KIDS (Kernel Installation & Distribution System) package to be installed on the VistA System MAG3_0P221_VIX_Setup.msi Installation file for the VIX software Version 30.221.5.6517 MAG3_0P221_Patch_ Description.pdf This document MAG3_0P221_VIX_ Installation_Guide.pdf VIX Installation Guide for this patch MAG3_0P221_User_Guide.pdf User Guide for this patch This patch installs the following software versions: Apache Tomcat: 8.0.52 Java: 8_0_171 version Documentation: -------------- This document provides an overview, explains the changes, and outlines the installation for this patch. Files & Fields Associated: -------------------------- File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- MAG WORK ITEM (#2006.941) Modified New C Cross Reference 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 -------- -------------------- MAGN PATIENT IMAGE LIST Modified MAGN PRECACHE BY CPT New Parameters Associated: Parameter Name New/Modified/Deleted -------------- -------------------- MAG PRECACHE ACQ ENABLED Modified MAG PRECACHE RAD REG ENABLED Modified Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A New Service Requests (NSRs): ------------------------------------- This project is initiated by Requirement BR 8.0 of the Health Information Exchange Viewer BRD #1-02-03-05-08-003. Patient Safety Issues (PSIs): ----------------------------- There are no patient safety issues associated with this patch. Supported SOP Classes ---------------------- The following table includes the newly supported SOP classes in MAG*3.0*221. The Hybrid DICOM Image Gateway (HDIG) validates the objects associated with these classes and stores them in the new database that then can be viewed via the new Image Viewer. Each SOP class must be enabled individually to be stored. The patch distributes all SOP classes disabled as the default. To enable the storage of new SOP classes, please enter a ServiceNow ticket, or contact the National Help Desk to request assistance from the CLIN3 Support Team. NOTE: Newly Supported SOP Classes are not currently viewable with Clinical Display or VistARad. SOP Classes Newly Supported in MAG*3.0*221 SOP Class Name SOP Class UID -------------- ------------- X-Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1 Enhanced SR 1.2.840.10008.5.1.4.1.1.88.22 Enhanced MR Color Image Storage 1.2.840.10008.5.1.4.1.1.4.3 Enhanced XA Image Storage 1.2.840.10008.5.1.4.1.1.12.1.1 Breast Tomosynthesis Image Storage 1.2.840.10008.5.1.4.1.1.13.1.3 Ophthalmic Photography 8 Bit Image Storage 1.2.840.10008.5.1.4.1.1.77.1.5.1 Basic Text SR 1.2.840.10008.5.1.4.1.1.88.11 Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. Defect 961648 - VRAD Users impacted by Patch 201 Problem: The VRAD problem occurred when VRAD tried to retrieve cached metadata. Resolution: ImagingExchangeCache-01.jar fixes the VRAD issue. 2. Defect 961600 - ROI Password change not working as expected in Patch 201 Problem: Release of Information (ROI) errors processing periodic commands. The system was unable to start periodic commands because the ROI service account credentials are invalid. Resolution: The fix was made in the ROIWebApp - ROI was modified to update both the ROIPeriodicCommandConfiguration.config and PeriodicCommandConfiguration.config files. 3. Defect 970712 - Precache entries in #2006.941 "MAG WORK ITEM" Problem: Precaching should not be occurring Resolution: Routine MAGNWRK1 has been updated to prevent a new PRECACHE work item being created during P34 object acquisition. 4. Defect 963272 - Issues found during IOC at San Diego Problem: QA Review Slow performance caused by image compression issue Resolution: ImageConversion-01.jar fixes the performance issue by handling DICOM compression issue. Test Sites: ------------- San Diego, CA Baltimore, MD Iron Mountain, MI Mountain Home, TN Software and Documentation Retrieval Instructions: -------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS software directory at the following OI Field Offices: Hines domain.ext Salt Lake City domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ Name File FTP Mode ---- ---- -------- MAG*3.0*221 KIDS MAG3_0P221.KID ASCII MAG*3.0*221 VIX Setup MAG3_0P221_VIX_Setup.msi Binary Version 30.221.5.6517 MAG*3.0*221 Patch MAG3_0P221_Patch Description.pdf Binary Description MAG*3.0*221 VIX MAG3_0P221_VIX_Installation Binary _Guide.pdf Patch Installation: Pre/Post Installation Overview: ------------------------------- See MAG*3.0*221 VIX Installation Guide for additional information. **Note** - There is an important Post Installation Step that must be completed after the installation of the KIDs and BEFORE the installation of the VIX msi. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Imaging/Patches/MAG_3.0_221

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

Patch Subject: MULTIPLE LINE ITEMS WITH 1ST SERVICE DATE; BILLING FACILITY NAME DISCREPANCY Description: ============ This patch addresses the following issues: -Insurance claims with multiple service line items/dates on the bill are not electronically transmitted properly. -The BILLING FACILITY NAME (#200) field in the INSTITUTION (#4) file is not correctly populated on the uniform billing form UB-04 FL-1. 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 Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Additional Information: N/A New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC3318511 - Insurance claims with multiple line items/dates on a single bill are not transmitting electronically properly. Problem: -------- Insurance claims on the bill in the Electronic Data Interchange (EDI) Transmission, displays only the first date of service listed on all service line items instead of an individual date of service for each service line item. Resolution: ------------ Routine IBCEFG1 was modified to pull the procedure date to the 'Service Date From' field for each service line item for the EDI transmission if it can be determined by the associated procedure, otherwise it will use the start date of the statement on the bill. 2. INC3333745 - Billing Facility Naming discrepancy resulting in denied claims for NCCPAC. Problem: -------- The BILLING FACILITY NAME (#200) field in the INSTITUTION (#4) file does not display to the correct uniform billing form, UB-04 FL-1, resulting in claims being denied by payers. Resolution: ----------- Post-init routine IB20P644, was created to modify the FORMAT CODE (#1) field in the IB FORM FIELD CONTENT (#364.7) file for the BILLING PROVIDER NAME (FL-1/1) form field. If the BILLING FACILITY NAME (#200) field of the INSTITUTION (#4) file exists, the Facility Name will be used. If not, the NAME (#.01) field of the INSTITUTION (#4) file will be used for the UB-04 FL-1 uniform billing form. TEST SITES: ----------- MARTINSBURG VAMC VA MARYLAND HCS Software and Documentation Retrieval Instructions: -------------------------------------------------- N/A Pre/Post Installation Overview: 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_644

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

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

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

Patch Subject: Bug fix in Entity Mapping utility Description: ============ Patch 16 correct 6 issues. Issues 1,2, & 3 were discovered during pre-load of the Veteran's Data Integration & Federation (VDIF) Qualifying Patient Query (QPQ) endeavor and the other three are fixes from patch DI*22.2*9. 1. Text containing $C(0) control characters. 2. Text larger than 3 megabytes. 3. Text containing "[[>" creates problem with XML 4. Missing DDE AUTO GEN ENTITY FOR A DD # option 5. Missing DDE ENTITY INQUIRE option 6. Seventeen field names were changed to conform to similar fields in other Infrastructure files. The DDE ENTIRY ENTER/EDIT form was changed to support the new field names. Patch Components: ----------------- File Name (#) Field Name (#) New/Modified/Deleted ------------- -------------------- ------------- ENTITY (#1.5) GET ENTRY ACTION (2) Modified GET EXIT ACTION (3) GET ID ACTION (4) PUT ENTRY ACTION (6) PUT EXIT ACTION (7) PUT ID ACTION (8) PUT CREATE ACTION (10) DELETE ENTRY ACTION (11) DELETE EXIT ACTION (12) DELETE ID ACTION (13) POST ENTRY ACTION (14) POST EXIT ACTION (15) POST ID ACTION (16) POST CREATE ACTION (18) SubDD ITEM (#1.51) GET ACTION (6) PUT ACTION (7) POST ACTION (8) Form Name File # New/Modified/Deleted --------- ------ -------------------- DDE ENTITY ENTER/EDIT 1.5 Modified Option Name Type New/Modified/Deleted ----------- ---- -------------------- Entity Mapping menu Modified [DDE ENTITY MAPPING] Inquire to Entity File option New [DDE ENTITY INQUIRE] Auto Gen Entity For A DD # option New [DDE AUTO GEN ENTITY FOR A DD #] Blood Bank Clearance: --------------------- 6/12/2019 EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch DI*22.2*16 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*16 have no adverse effect on Blood Bank software functionality, therefore RISK is none. Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. Problem: Word processing and free text fields can contain control characters Resolution: Change DDEG to remove control characters 2. Problem: Word processing fields can exceed 3 million characters Resolution: Change DDEG to remove text and replace with phrase: "Text exceed 3 megabyte limit and could not be saved. Please contact the site for full original text." 3. Problem: Word processing can contain "[[>" string which creates problems for XML Resolution: Change DDEG to remove string 4. Problem: Missing DDE AUTO GEN ENTITY FOR A DD # option Resolution: Add missing option 5. Problem: Missing DDE ENTITY INQUIRE option Resolution: Add missing option 6. Problem: Fields have non-conforming names Resolution: Change 17 field names Test Sites: ----------- West Palm Beach, FL North Chicago, IL Software and Documentation Retrieval Instructions: -------------------------------------------------- Software is being released as a KIDS Build on Forum. Patch Installation: Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/VA+FileMan/Patches/DI_22.2_16

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

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

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

Patch Subject: FY20 CHARS CODE CHANGES Description: ============ Patch ECX*3.0*175 updates the SHORT DESCRIPTION (#1) field of four existing entries in the NATIONAL CLINIC (#728.441) file. ************************************************************************* NOTE: This patch has a shortened compliance date because it must be installed as close to 10/1/2019 as possible. Sites will need the updates for Fiscal Year (FY) 20. ************************************************************************* Patch Components: ----------------- Files & Fields Associated: N/A 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 Remote Procedures Associated: N/A Parameter Definitions Associated: N/A Additional Information: Blood Bank Team Coordination: ----------------------------- N/A New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC5882411 - FY20 CHAR4 CODE CHANGES FOR NATIONAL CLINIC (#728.441) FILE Problem: -------- A request was made by the Managerial Cost Accounting Office (MCAO) to update the SHORT DESCRIPTION (#1) field of four existing entries in the NATIONAL CLINIC (#728.441) file. Resolution: ----------- Routine ECX3P175 has been created to update the NATIONAL CLINIC (#728.441) file by modifying the SHORT DESCRIPTION (#1) field of four existing entries effective 10/1/2019. The descriptions of the following entries have changed: Existing Code New Short Description ------------- --------------------- DE00 SVH Telehealth (StateVetHom) HTAC Take Chrg MyLife&Hlth Grp IDHC Whole Health Clinical Care RFLX Intro to Whole Health Test Sites: ---------- Boston Louisville Software and Documentation Retrieval Instructions: ---------------------------------------------------- N/A Patch Installation: Pre/Post Installation Overview: ------------------------------- You may install this patch at any time without interruption to users. It should take less than 2 minutes to install this patch. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/DSS+Extracts/Patches/ECX_3.0_175

Update per VistA convergence conference calls Nov/Dec 2013

392b806

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update per VistA convergence conference calls Nov/Dec 2013 #1

Update per VistA convergence conference calls Nov/Dec 2013 #1

ksbhaskar commented Dec 14, 2013

ChristopherEdwards commented Dec 16, 2013

Update per VistA convergence conference calls Nov/Dec 2013 #1

Are you sure you want to change the base?

Update per VistA convergence conference calls Nov/Dec 2013 #1

Conversation

ksbhaskar commented Dec 14, 2013

ChristopherEdwards commented Dec 16, 2013