Update per VistA convergence conference calls Nov/Dec 2013 by ksbhaskar · Pull Request #1 · WorldVistA/VistA-M

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: MID-FY17 CHANGES FOR 4 CHAR CDS NATIONAL CLINIC (#728.441) FILE Description: ============ Patch ECX*3.0*165 updates the SHORT DESCRIPTION (#1) field of 10 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/2017 as possible. Sites will need the updates for mid - Fiscal Year (FY) 17. ************************************************************************* ASSOCIATED NSR: =============== N/A ASSOCIATED TICKET: ================== I10617601FY16 - Mid-FY17 Changes for 4 Char Cds (National Clinic #728.441 file) PARTICIPATING TEST SITES: ========================= Providence VA Medical Center Carl Vinson VA Medical Center (Dublin) TICKET OVERVIEW: ================ I10617601FY16 - Mid-FY17 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 10 existing entries in the NATIONAL CLINIC (#728.441) file. Resolution: ----------- Routine ECX3P165 has been created to update the NATIONAL CLINIC (#728.441) file by modifying the SHORT DESCRIPTION (#1) field of 10 existing entries effective 4/1/2017. The descriptions of the following entries have changed: Existing Code New Short Description ------------- --------------------- CDTC Expressive Arts CGQC Qi Gong DEMC Eye Mvmnt Desensitiz&Reprocess HTFC Whole Health Partner IACT BFA Technique (not regular Acupuncture) IDHC Integrative Health Consult MMMT Mindfulness other than MBSR MPAT Movement Therapy PNTC Animal-Assisted Therapy WCHC Whole Health Coaching 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_165

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

Patch Subject: Immunization Health Summary Enhancements Description: ============ ======================================================================= This patch must be installed after PX*1.0*210 ======================================================================= The Veterans Health Information Systems and Technology Architecture (VistA) Immunizations Enhancements (VIMM) 2.0 project modifies existing files and adds additional files to enable VA to quickly and reliably document and exchange standardized skin test and immunization information on beneficiaries across services and departments. Additionally, modifications support VistA Evolution requirements. This provides a Veteran patient-centric vaccine record exchangeable with the external community. Clinicians will have access to a more complete medical history in the VistA electronic medical record resulting in improved health status as well as public health monitoring. The goals for the VIMM 2.0 project are to deliver an Initial Operating Capability comprised of standard, interoperable skin test and immunization data for exchange with external trading partners based on the modernization of the VistA Patient Care Encounter (PCE) package. The existing PCE Immunizations Health Summary is modified and four new Immunization components are added in this patch. The new Health Summary features include: 1. IM - PCE IMMUNIZATIONS (Existing) The format of the existing Immunizations Health Summary report has been modified to display the standard Name implemented in PX*1.0*201 in place of the short name. Information about reactions and contraindications has been re-formatted as well. If an immunization is associated with a reaction and/or contraindication, a '<**>' is displayed at the end of the line under 'Reaction'. Complete details about the reaction and/or contraindication appear in a footnote at the bottom of the report. If the record has a comment, a '<C> is displayed under 'Info'. Comments no longer appear on this report but can be viewed in the Detailed Immunizations Health Summary component. 2. SIM - PCE IMMUNIZATIONS SELECTED (New) The new SIM Health Summary report allows a user to select immunizations as well as time and occurrence limits. The user can select an unlimited number of the immunizations defined in the Immunization (#9999999.14) file. The user may select a time limit up to 99 years and 999 maximum occurrences. Individual records are displayed in alphabetical order by immunization name and then by administration date in reverse chronological order. The format of the display is the same format used in the PCE IMMUNIZATIONS Health Summary (IM). The report displays immunization name, series, administration date and facility. If there is a reaction and/or contraindication, the record is marked with a '<**>'. The name of the immunization, date of administration and reaction/contraindications are displayed at the end of the display. If the record has a comment it is marked with a <C>. Comments can be viewed in the Detailed Immunizations Health Summary component. 3. DIM - PCE IMMUNIZATIONS DETAILED (New) DIM is a new Health Summary report that presents twenty-five immunization data elements in a Fileman captioned style. The data elements include: immunization name, full name, series, administration date, facility, reaction, contraindications, manufacturer, lot number, expiration date, dosage, administration route, administration site, vaccine information statements offered to the patient, administered by, ordered by, documented by, comments, results, reading, date read, reader, reading recorded, hours read post-inoculation, and reading comment. Individual immunization records are sorted in alphabetical order by immunization name and then by administration date in reverse chronological order. 4. SIMR - PCE IMMUN SELECT REVERSE CHRON (New) SIMR is a new Health Summary report that also allows the user to select immunizations and time and occurrence limits. Individual immunization records are sorted in reverse chronological order and then alphabetically by immunization name. The user is allowed to select any of the immunizations defined in the Immunization (#9999999.14) file. The user may select a time limit up to 99 years and 999 maximum occurrences. The format of the SIMR display is the same format used in the PCE IMMUNIZATIONS Health Summary (IM). 5. SIMC - PCE IMMUNIZATIONS SELECT CHRON (New) SIMC is a new Health Summary report that allows the user to select immunizations as well as time and occurrence limits. Individual immunization records are sorted in chronological order and then alphabetically by immunization name. The format of the display is the same format used in the PCE IMMUNIZATIONS Health Summary (IM). Patch Components: ----------------- APIs Associated: API New/Modified/Deleted -------------- -------------------- N/A Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- HEALTH SUMMARY TYPE (#142) STRUCTURE (multiple Modified field #1, sub-file 142.01) SELECTION ITEM (#4) of the STRUCTURE sub-file (#142.01) 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 RPCs Associated: RPC 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 Remedy Ticket(s) & Overview: ---------------------------- N/A Test Sites: ---------- Cleveland, OH Hampton, VA Heartland-East HCS, MO San Antonio, TX Software and Documentation Retrieval Instructions: ---------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ Title File Name FTP Mode ---------------------------------------------------------------- Health Summary V. 2.7 User HSUM_2_7_UM.PDF (binary) Manual Health Summary V. 2.7 Technical HSUM_2_7_TM.PDF (binary) Manual Patch Installation: Pre/Post Installation Overview: ------------------------------- A post install routine, GMTSP114 creates the four new Health Summary components and adds them to the Ad Hoc Health Summary. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Health+Summary/Patches/GMTS_2.7_114

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 (#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/master/Packages/National+Drug+File/Patches/PSN_4.0_471

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: GREATER THAN 90 DAYS SUPPLY ENHANCEMENT Description: ============ This patch is part of the Pharmacy Safety Updates project which was established to address specific New Service Requests (NSRs) as well as Remedy Ticket(s) and a Patient Safety Issue (PSI) related to the VistA Pharmacy applications as approved by the Health Systems Enterprise Systems Manager(ESM). This project is comprised of patches from five different applications, as shown below: APPLICATION/VERSION PATCH ----------------------------------------------------------------- PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*189 OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*444 INPATIENT MEDICATIONS (IM) V.5.0 PSJ*5*313 NATIONAL DRUG FILE (NDF) V. 4.0 PSN*4*429 INTEGRATED BILLING (IB) V. 2.0 IB*2*545 The following New service Requests (NSRs), Remedy Ticket(s) and Patient Safety Issue (PSI) are being addressed by this patch: NSRs 20060601/20111206 Allow Dispensing of Greater Than 90 Day Supply PSI PSPO00002098 Need to be able to enter greater than 90-days supply on medications that only come in units designed to last greater than 90 days --------------------------------------------------------------------------- The Outpatient Pharmacy and supporting VistA applications are being modified to allow dispensing of more than 90 day supply fill for outpatient prescriptions. The new limit will be 365 days and will be set for each drug individually. See below for more information on specific menu options related to this enhancement. ========================================================================= PSI PSPO00002793 Patient Prescription Processing error, truncating the second character of the Days Supply Remedy 387051 Patient Medication Profile Bad Address Indicator display ---------------------------------------------------------------------------- The Outpatient Pharmacy Medication Profile has a display problem for a prescription with the following characteristics: 2-letter status (e.g., DC), drug marked for Consolidated Mail Outpatient Pharmacy (CMOP) and Bad Address Indicator. When a prescription with all three features is displayed the DAY SUP column value is being truncated as illustrated below where the Day Supply value is actually 90 and it displays as 9. ISSUE LAST REF DAY # RX # DRUG QTY ST DATE FILL REM SUP --------------------------------DISCONTINUED-------------------------------- 1 100005604$ TOBRAMYCIN 80MG/2ML INJ 100 DC>B01-21 01-21 0 9 ========================================================================= Remedy 1049220 Outpatient Pharmacy - Electronic Prescribing of CS (ePCS) ------------------------------------------------------------------------ Control substance (TRAMADOL) defaulting to 90 supply instead of 30. ========================================================================= This patch modifies the Outpatient Pharmacy application regarding the enhancements and issues listed above: 1. Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option a) The backdoor pharmacy was modified to accept the new maximum value for the DAYS SUPPLY field based on the limit set by the MAXIMUM DAYS SUPPLY field (#66) introduced in patch PSS*1*189 in the DRUG file (#50) or the MAXIMUM DAYS SUPPLY field (#32) introduced in patch PSN*4*429 in the VA PRODUCT (#50.68) file. If alternate maximum values do not exist, the current limits will remain the same. Note: The MAXIMUM DAYS SUPPLY field (#32) added to the VA PRODUCT file (#50.68) is being introduced by patch PSN*4*429, however it will not be populated initially by the Pharmacy Product System - National (PPS-N) as changes will be required to that application to edit and export this new field. b) The medication profile was modified to display the Bad Address Indicator in a different line in order to address the Remedy Ticket 387051 and Patient Safety Issue PSPO00002793 mentioned above. The indicator will be placed in the next line, as seen below. ----------------------------------ACTIVE--------------------------------- 1 100005598 ALSEROXYLON 2MG TAB 400 A> 12-11 03-01 2 90 **Bad Address** 2 100005596 DESIPRAMINE 25MG TAB 90 DC 11-01 11-01 11 30 **Bad Address** 3 100005601A NAPROXEN 250MG S.T. 170 HP>12-17 12-17 5 30 **Bad Address** 4 100005595 TIMOLOL 0.25% OPTH SOL 10ML 90 S> 11-01 11-21 10 30 c) The calculation of the number of refills for a prescription was modified to take into account the new maximum value allowed for the DAYS SUPPLY field. The current calculation (up to 90 days supply) will remain the same and a new formula will be introduced to calculate the number of refills for days supply values of 91 up to 365. The table below shows the number of refills allowed based on the days supply value: ---------------------------------+------------------------------------ NON-CONTROLLED SUBSTANCES | CONTROLLED SUBSTANCES (NO CHANGE) ---------------+-----------------+------------------+----------------- DAYS SUPPLY | # OF REFILLS | DAYS SUPPLY | # OF REFILLS ---------------+-----------------+------------------+----------------- 1 - 59 | 11 | 1 - 59 | 5 60 - 89 | 5 | 60 - 89 | 2 90 - 91 | 3 | 90 | 1 92 - 121 | 2 | | 122 - 182 | 1 | | 183 - 365 | 0 | | ---------------+-----------------+------------------+---------------- 2. Complete Orders From OERR [PSO LMOE FINISH] option This option was modified to accept the new maximum value for the DAYS SUPPLY field based on the limit set by the MAXIMUM DAYS SUPPLY field (#66) in the DRUG file (#50) or the MAXIMUM DAYS SUPPLY field (#32) in the VA PRODUCT (#50.68) file. If alternate maximum values exist, the current limits will remain the same. 3. Edit Prescriptions [PSO RXEDIT] option This option was also modified to accept the new maximum value for the DAYS SUPPLY field based on the limit set by the MAXIMUM DAYS SUPPLY field (#66) in the DRUG file (#50) or the MAXIMUM DAYS SUPPLY field (#32) in the VA PRODUCT (#50.68) file. If alternate maximum values exist, the current limits will remain the same. 4. Barcode Batch Prescription Entry [PSO BATCH BARCODE] option The renewal functionality within this option was also modified to accept the new maximum value for the DAYS SUPPLY field based on the limit set by the MAXIMUM DAYS SUPPLY field (#66) in the DRUG file (#50) or the MAXIMUM DAYS SUPPLY field (#32) in the VA PRODUCT (#50.68) file. If alternate maximum values exist, the current limits will remain the same. 5. Prescription Management Data Compilation The algorithm used to compile prescription management data was modified to account for prescriptions with greater than 90 days supply. The OVER 90 DAYS (#8) field in the OUTPATIENT PHARMACY MANAGEMENT DATA file (#59.12), which is used as a counter for the number of prescription fills with DAYS SUPPLY value greater than 90, will now be populated. 6. Count of Prescriptions [PSO MGMT REPORT RX COUNTS] option & Count of Prescriptions [PSO MGMT MONTHLY RX COUNTS] option These daily and monthly reports have been modified to include a new column called ">90 DAY", as seen below. This column will display the total number of prescription fills with a DAYS SUPPLY value greater than 90, as shown below. 30 60 90 >90 EQ TOT TOT DAY DAY DAY DAY FLS METH RX EQ FL ...===========================================================... 1 3 0 1 11 0 5 11 0 0 1 2 14 0 3 14 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ...=== ======= ======= ======= ======= ======= ======= =======... 1 3 1 3 25 3 8 25 Patch Components ================ Files & Fields Associated: File Name (#) Field Name (#) New/Modified/Deleted ------------------ ----------------------------------- -------------------- PRESCRIPTION (#52) DAYS SUPPLY (#8) Modified RETURN TO STOCK LOG (#52.07) DAYS SUPPLY (#4) Modified REFILL (#52.1) DAYS SUPPLY (#1.1) Modified PENDING OUTPATIENT ORDERS (#52.41) DAYS SUPPLY (#101) Modified Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name New/Modified/Deleted ------------- -------------------- N/A Templates Associated: Template Name Type File Name (#) New/Modified/Deleted ------------- ---- ------------- -------------------- N/A New Service Requests (NSRs): ---------------------------- 20060601 20111206 Patient Safety Issues (PSIs): ----------------------------- PSPO00002793 PSPO00002098 Remedy Ticket(s) & Overviews: ----------------------------- 387051-Patient Medication Profile Bad Address Indicator display 1049220-Outpatient Pharmacy - Electronic Prescribing of CS (ePCS) TEST Sites: =========== LOUISVILLE, KY NEW YORK HARBOR HCS HEARTLAND EAST 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 Documentation can also be retrieved from the VA Software Documentation Library (VDL) on the Internet at the following address: http://www4.domain.ext/vdl. File Description File Name FTP Mode -------------------------------------------------------------------------- OUTPATIENT PHARMACY PHARMACIST'S USER PSO_7_PHAR_UM_R0616.DOC ASCII MANUAL Patch Installation: Pre Installation Overview -------------------------- This project is comprised of patches from five different applications as listed here. The patches will get released together and the suggested installation order is as shown. An installation guide released with patch PSS*1*189, discusses the installation process as PSS*1*189 is the patch that must be installed first. APPLICATION/VERSION PATCH ----------------------------------------------------------------- PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*189 OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*444 INPATIENT MEDICATIONS (IM) V.5.0 PSJ*5*313 NATIONAL DRUG FILE (NDF) V. 4.0 PSN*4*429 INTEGRATED BILLING (IB) V. 2.0 IB*2*545 ----------------------------------------------------------------- Post Installation Overview -------------------------- N/A 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_444

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: 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 (#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/master/Packages/Integrated+Billing/Patches/IB_2.0_529

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

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

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

Patch Subject: 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: 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 (#1.01) New AUTO-DECREASE RX ENABLED (#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/master/Packages/Accounts+Receivable/Patches/PRCA_4.5_304

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

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

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

Patch Subject: 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: 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 15 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*59 and RG*1.0*61 are required builds for patch RG*1.0*64. NOTE: Master Patient Index (MPI) enhancements are being distributed in three VistA namespaces: DG, RG and MPIF. RG*1.0*64 has no dependencies on the other 2 patches (DG*5.3*919, MPIF*1.0*62) and can be installed any time. Issue #1 Modifications were made to routine RGADTP2 to prevent A31 Health Level Seven (HL7) patient update messages from the Master Veteran Index (MVI) from being processed when the patient is currently admitted as an inpatient at the site. This ensures that any data discrepancies that might have been present in these messages do NOT impact direct patient care for admitted patients at the site. However, it does NOT prevent the site from updating their own patient record even if the patient is currently admitted as an inpatient. (Ex. Patient data changes could cause a conflict with a patient's wristband.) Note: An Application Accept (AA) response to the A31 HL7 update message will be returned to MVI indicating the patient's 'inpatient' admission status and no further processing of the message will occur at the site. Issue #2 Modifications were also made to routine RGADTP1 to prevent A31 HL7 patient update messages from the Veterans Benefits Administration (VBA) [200CORP, 200BRLS sites] from incorrectly populating the PREFIX (#4) and SUFFIX (#5) fields in the NAME COMPONENTS (#20) file by reversing the contents. This incorrect population caused filing and displaying issues of the NAME (#.01) field in the PATIENT (#2) file and could have also caused issues with the NAME (#.01) field of the ALIAS (#1) sub-file. Note: With name standardization, the prefix should never be filed into the NAME (#.01) field of the PATIENT (#2) file. 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: ---------- C.W. Bill Young (Bay Pines) VAMC Robley Rex (Louisville) VAMC VA Connecticut HCS Patch Installation: Pre/Post Installation Overview ------------------------------ There are no Pre/Post installation routine processes. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Clinical+Information+Resource+Network/Patches/RG_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: MID-FY16 CHANGES FOR 4 CHAR CDS NATIONAL CLINIC (#728.441) FILE Description: ============ Patch ECX*3.0*159 adds 4 new entries and updates the SHORT DESCRIPTION (#1) field of 11 existing entries in the NATIONAL CLINIC (#728.441) file. ************************************************************************* NOTE: This patch has a shortened compliance date because it must be installed on 4/1/2016. Sites will need the updates for Mid Fiscal Year (FY) 16. ************************************************************************* ASSOCIATED NSR: =============== N/A ASSOCIATED TICKETS: =================== 1. I5840930FY15 - Mid-FY16 Changes for 4 Char Cds (National Clinic #728.441 file) PARTICIPATING TEST SITES: ========================= PROVIDENCE VAMC LOUISVILLE VAMC NFSG (GAINESVILLE, LAKE CITY) TICKET OVERVIEW: ================ 1. I5840930FY15 - Mid-FY16 Changes for 4 Char Cds (National Clinic #728.441 file) Problem: -------- A request was made by the Managerial Cost Accounting Office (MCAO) to add 4 new entries and update the SHORT DESCRIPTION (#1) field of 11 existing entries in the NATIONAL CLINIC (#728.441) file. Resolution: ----------- Created routine ECX3P159 to update the NATIONAL CLINIC (#728.441) file by adding 4 new entries and modifying the SHORT DESCRIPTION (#1) field of 11 existing entries effective 4/1/2016. The following entries will be added: Code Short Description -------------- ------------------------- LVL6 Mobile Medical Unit 6 LVL7 Mobile Medical Unit 7 LVL8 Mobile Medical Unit 8 LVL9 Mobile Medical Unit 9 The descriptions of the following entries have changed: Existing Code New Short Description --------------- ------------------------- LVL1 Mobile Medical Unit 1 LVL2 Mobile Medical Unit 2 LVL3 Mobile Medical Unit 3 LVL4 Mobile Medical Unit 4 LVL5 Mobile Medical Unit 5 PNPC PACT CVT-H Physician PNQC PACT CVT-H Physician Assistant PNRC PACT CVT-H Nurse Practitioner PNSC PACT CVT-H Nurse RDNU Radiology Oncology Clinic SNRC VA Provider & Pt at NonVAFacility 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_159

Patch Subject: VIAB INCREMENT 1 UPDATES Description: ============ The VistA integration Adaptor (VIA) project requires access to certain Remote Procedure Calls (RPCs). The purpose of this patch is to publish those RPCs to the VIAB WEB SERVICES OPTION in the OPTION file (#19), RPC field (#320) which allows VIA to access. Three new RPC's have been created as replacements for RPC's that VIA could not obtain ICR's in order to use the RPC's. VIABPCE2 GET HFACTORS TYPE used in place of ORWPCE GET HEALTH FACTOS TY VIABCE4 LEX used in place of ORWPCE4 LEX VIABU EXTNAME used in place of ORWU EXTNAME 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 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. RPC (#320): ORALWORD ALLWORD ORCHECK GETXTRA ORDDPAPI CLOZMSG OREVNTX1 GETSTS ORQQCN STATUS ORQQCN SVC W/SYNONYMS ORWD1 PRINTGUI ORWD1 RVPRINT ORWD2 DEVINFO ORWDCN32 ORDRMSG ORWDPS1 FAILDEA ORWDPS1 ODSLCT ORWDPS2 DAY2QTY ORWDPS2 MAXREF ORWDPS2 QTY2DAY ORWDPS32 DRUGMSG ORWDPS32 ISSPLY ORWDPS32 VALQTY ORWDPS32 VALROUTE ORWDRA32 APPROVAL ORWDRA32 DEF ORWDX DGNM ORWDX2 DCREASON ORWDXA ISACTOI ORWDXR RNWFLDS ORWDXR01 CANCHG ORWGRPC ITEMDATA ORWGRPC ITEMS ORWOR1 GETDSCH ORWRP GET DEFAULT PRINTER ORWTPD GETDFLT TIU DETAILED DISPLAY TIU SET ADMINISTRATIVE CLOSURE VIABPCE2 GET HFACTORS TYPE VIABPCE4 LEX VIABU EXTNAME New Remote Procedure Calls: -------------------------- VIABPCE2 GET HFACTORS TYPE VIABPCE4 LEX VIABU EXTNAME Remote Procedure Calls modified: ------------------------------- ORALWORD ALLWORD ORCHECK GETXTRA ORDDPAPI CLOZMSG OREVNTX1 GETSTS ORQQCN STATUS ORQQCN SVC W/SYNONYMS ORWD1 PRINTGUI ORWD1 RVPRINT ORWD2 DEVINFO ORWDCN32 ORDRMSG ORWDPS1 FAILDEA ORWDPS1 ODSLCT ORWDPS2 DAY2QTY ORWDPS2 MAXREF ORWDPS2 QTY2DAY ORWDPS32 DRUGMSG ORWDPS32 ISSPLY ORWDPS32 VALQTY ORWDPS32 VALROUTE ORWDRA32 APPROVAL ORWDRA32 DEF ORWDX DGNM ORWDX2 DCREASON ORWDXA ISACTOI ORWDXR RNWFLDS ORWDXR01 CANCHG ORWGRPC ITEMDATA ORWGRPC ITEMS ORWOR1 GETDSCH ORWRP GET DEFAULT PRINTER ORWTPD GETDFLT TIU DETAILED DISPLAY TIU SET ADMINISTRATIVE CLOSURE New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Remedy Ticket(s) & Overview: ---------------------------- N/A Test Sites: ----------- Gulf Coast Northampton Central Alabama Documentation Retrieval Instructions: ------------------------------------- N/A Patch Installation: ------------------- Pre/Post Installation Overview: ------------------------------- Patch VIAB*1*3 must be installed prior to installation of VIAB*1*5. Patch OR*3*426 must be installed prior to installation of VIAB*1*5. Patch TIU*1*300 must be installed prior to installation of VIAB*1*5. 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_5

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: 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: VistA Scheduling Enhancement Release 2 Description: ============ ***************************** PLEASE NOTE ******************************** * * *The VHA Release Board has NOT provided approval for this patch to be * * installed in ANY production environment. * * * * NOTE: This patch is ONLY to be loaded into a TEST environment until * * approval from the VHA Release Board is obtained to load into facility * * production environments. * * * ************************************************************************** The Veterans Health Administration (VHA) Access and Clinic Administrative Program (ACAP) has requested an enterprise enhancement for the VistA Scheduling Package. The enhancement will reduce operating cost for VHA and improve operational efficiencies resulting in patient centered access to care, coordinated care, increased customer satisfaction, and the reduction of excessive cycle/wait time used for scheduling patients. This patch contains phase 2 of the server API support for the VistA Scheduling Client as follows: ** For inpatients, the VS GUI shall display ward location in patient demographic area for each patient. To support this change, ward location has been included in the Remote Procedure Call (RPC) 'SDEC GETREGA'. ** The VS GUI shall display special clinic instructions on the screen. The data from the SPECIAL INSTRUCTIONS multiple field (#1910) in the HOSPITAL LOCATION file (#44) is now returned in the RPC 'SDEC CLINSET' to support this change. ** Add Cancel to the SDEC ACCESS TYPE file (#409.823) and use that access type in the return for the RPC 'SDEC CSLOTSCH' when the availability has been cancelled. ** Do not return clinics in RPCs when the OCCASION OF SERVICE CLINIC? field in the HOSPITAL LOCATION file (#44) is defined as 'YES'. ** Add new RPC called 'SDEC APPSLOTS' to return availability string from VistA. ** Add W2VA - WELCOME TO VA to the Set of codes in the REQUEST TYPE field (#4) of the SDEC APPT REQUEST file (#409.85). ** Add the RPC 'SDEC NOAVAIL' to determine if availability has ever been defined for a given clinic. ** Add the multiple field VS AUDIT to the SD WAIT LIST file (#409.3) and SDEC APPT REQUEST file (#409.85). The RPCs 'SDEC WLSET' and 'SDEC ARSET' have been enhanced to support adds and updates to these new multiples. The RPCs 'SDECAR AUDITGET' and 'SDECWL AUDITGET' have been added to retrieve the data from these new multiples. ** OT4 Release 2 - Comp & Pension Appointments. Support for AMIE scheduling event driver. ** Updates to the RPCs 'SDEC APPADD', 'SDEC ARMRTSET', 'SDEC ARSET', and 'SDEC ARGET' have been implemented to support the PARENT/CHILD relationships between entries in the SDEC APPT REQUEST file (#409.85). ** Add the RPC 'SDECAPP GETYPE' to get the APPOINTMENT TYPE for the given SDEC APPOINTMENT id. ** Change the COMMENT field of the SDEC APPT REQUEST file (#409.85) to accept 80 characters instead of 60. ** Single Sign-on support for CALL CENTER. ** Updates to SSN formatted inputs in the RPC 'SDEC PTLOOKRS'. Patch Components ================ Files & Fields Associated: File Name (#) Field Name (#) NEW/MODIFIED/DELETED ------------- -------------- -------------------- SD WAIT LIST VS AUDIT New (#409.3) (#45) VS AUDIT sub-file DATE EDITED New (409.345) (#.01) VS AUDIT sub-file EDITED BY New (409.345) (#1) VS AUDIT sub-file WL SPECIFIC CLINIC New (409.345) (#2) VS AUDIT sub-file WL SPECIFIC HOSPITAL LOCATION New (409.345 (#3) VS AUDIT sub-file WL SERVICE/SPECIALTY New (409.345) (#4) SDEC APPT REQUEST REQUEST TYPE Modified (#409.85) (#4) MULT APPTS MADE sub-file PARENT REQUEST New (409.852) (#.02) SDEC APPT REQUEST VS AUDIT New (409.85) (#45) VS AUDIT sub-file DATE EDITED New (409.8545) (#.01) VS AUDIT sub-file EDITED BY New (409.8545) (#1) VS AUDIT sub-file REQ SPECIFIC CLINIC New (409.8545) (#2) VS AUDIT sub-file REQ SERVICE/SPECIALTY New (409.8545) (#3) 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 ------------- ---- ------------------ -------------------- N/A Additional Information: N/A New Service Requests (NSRs): ----------------------------- N/A Patient Safety Issues (PSIs): ------------------------------ N/A Remedy Ticket(s) & Overviews: ----------------------------- N/A Test Sites: ----------- Asheville Chillicothe Hudson Valley Salt Lake City Software and Documentation Retrieval Instructions: -------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: domain.ext Hines: domain.ext Salt Lake City: domain.ext> The documentation will be in the form of Adobe Acrobat files. Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ File Description File Name FTP Mode -------------------------------------------------------------------------- SCHEDULING Technical Manual VSE_TM.PDF (binary) Patch Installation in TEST ONLY ***DO NOT INSTALL INTO PRODUCTION***: Pre/Post Installation Overview ------------------------------ The Post-Installation routine does the following functions: 1. Registers the new RPCs to the SDECRPC option 2. Adds CANCELLED entry to the new SDEC ACCESS TYPE 3. Initializes new Mumps cross-references: - "AC" in the SDEC RESOURCE file (#409.831) - "AC" in the SDEC APPOINTMENT file (#409.84) 4. Add/update entry in the REMOTE APPLICATION file (#8994.5) for VS SCHEDULING CALL CENTER Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/master/Packages/Scheduling/Patches/SD_5.3_642

Patch Subject: DSS FY 2016 SUSTAINMENT UPDATE Description: ============ Since the release of the DSS FY 16 Annual Sustainment patch ECX*3*154, there have been a couple of issues identified. The first issue is with the CBOC Activity Report. The clinic data was moved in the CLINIC EXTRACT file (#727.827) and the report uses that information to group data on the report. Extracts created using the FY16 logic will no longer have clinic data in the old location, which will cause an error in this report. The second issue is with the logic for determining if a medication given throug BCMA is considered a multi-dose medication. The multi-dose logic is applied to both unit dose type medications as well as IV type medications. The logic is being modified so it only applies to unit dose type medications. This patch will correct these issues. Problem #1: CBOC Activity report causes an error. ASSOCIATED CA Service Desk: ========================== I6535680FY16 ASSOCIATED NSR: =============== N/A Problem: -------- When a user attempts to run the CBOC Activity Report and selects an extract that was created using the FY16 logic, the report throws an error and kicks the user off the system. Resolution: ----------- The routine ECXUCBOC was updated so that the clinic information is obtained from the correct location depending on the fiscal year logic used to create the extract. Problem #2: Certain IV orders are being missed by the BCMA extract ASSOCIATED CA Service Desk: ========================== I6680642FY16 ASSOCIATED NSR: =============== N/A Problem: -------- After release of the patch, it was determined that the logic for determining multi-dose containers shouldn't apply to IV type orders. In general, only unit dose type orders are delivered in multi-dose containers so the logic should only apply to those types of orders. In addition, BCMA records with a status of infusing will now be considered for inclusion in the extract. Resolution: ----------- The logic in routine ECXBCM was changed so that a check is made to determine if the order being processed in the BCMA extract is an IV or a unit dose type order. If it's an IV type order the check to determine if the order is a multi-dose order is not applied. Also, all BCMA records with a status of infusing are now considered for inclusion in the extract. The result is that all IV orders will be counted when doing the BCMA extract. Test Sites: ----------- Boston Little Rock Alexandria INSTALLATION: ============= If installed during the normal workday, it is recommended that the following selection(s) in the OPTION (#19) file, and all of their descendants be disabled to prevent possible conflicts while running the KIDS Install. Other VISTA users will not be affected. Extract Manager's Options [ECXMGR] Install Time - less than 2 minutes (unless otherwise indicated) *********************************************************** 1. LOAD TRANSPORT GLOBAL --------------------- Choose the PackMan message containing this patch and invoke the INSTALL/CHECK MESSAGE PackMan option. 2. START UP KIDS ------------- Start up the Kernel Installation and Distribution System Menu [XPD MAIN]: Edits and Distribution ... Utilities ... Installation ... Select Kernel Installation & Distribution System Option: INStallation --- Load a Distribution Print Transport Global Compare Transport Global to Current System Verify Checksums in Transport Global Install Package(s) Restart Install of Package(s) Unload a Distribution Backup a Transport Global Select Installation Option: 3. Select Installation Option: -------------------------- NOTE: The following are OPTIONAL (When prompted for the INSTALL NAME, enter ECX*3.0*160): a. Backup a Transport Global - This option will create a backup message of any routines exported with this patch. It will not backup any other changes such as DD's or templates. b. Compare Transport Global to Current System - This option will allow you to view all changes that will be made when this patch is installed. It compares all components of this patch (routines, DD's, templates, etc.). c. Verify Checksums in Transport Global - This option will allow you to ensure the integrity of the routines that are in the transport global. 4. Select Installation Option: Install Package(s) ---------------- **This is the step to start the installation of this KIDS patch: a. Choose the Install Package(s) option to start the patch install. Enter ECX*3.0*160 when prompted for a build name. b. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//' answer NO. c. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//' answer YES. d. When prompted 'Enter options you wish to mark as 'Out Of Order':' Enter the following options: Extract Manager's Options [ECXMGR] e. If prompted 'Enter protocols you wish to mark as 'Out Of Order':' press <return>. f. If prompted 'Delay Install (Minutes): (0-60): 0//' answer "0" (unless otherwise indicated). Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;DSS EXTRACTS;**[Patch List]**;Dec 22, 1997 ;Build 1 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: ECXBCM Before: B95494822 After: B97333580 **107,127,132,136,143,144,148, 149,154,160** Routine Name: ECXUCBOC Before: B95678239 After: B98139250 **49,148,149,160** Routine list of preceding patches: 154 ============================================================================= User Information: Entered By : Date Entered : NOV 17, 2015 Completed By: Date Completed: APR 29, 2016 Released By : Date Released : MAY 02, 2016 ============================================================================= Packman Mail Message: ===================== $END TXT 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_160

Update per VistA convergence conference calls Nov/Dec 2013

392b806

Navigation Menu

Uh oh!

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

Update per VistA convergence conference calls Nov/Dec 2013#1
ksbhaskar wants to merge 1 commit into
WorldVistA:masterfrom
ksbhaskar:patch-1

ksbhaskar commented Dec 14, 2013

Uh oh!

ChristopherEdwards commented Dec 16, 2013

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

ksbhaskar commented Dec 14, 2013

Uh oh!

ChristopherEdwards commented Dec 16, 2013

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants