$TXT Created by DEVVCC.DOMAIN.EXT (KIDS) on Thursday, 11/03/16 at 10:29 ============================================================================= Run Date: DEC 19, 2016 Designation: IB*2*579 Package : IB - INTEGRATED BILLING Priority: EMERGENCY Version : 2 SEQ #534 Status: Released Compliance Date: DEC 22, 2016 ============================================================================= Associated patches: (v)IB*2*549 <<= must be installed BEFORE `IB*2*579' Subject: MCCF EINSURANCE FY15 549 WARRANTY Category: - Routine - PATCH FOR A PATCH Description: ============ *** Note: This patch has a mandatory 3 day installation compliance. The purpose of this patch is to meet the requirements of the Medical Care Collection Fund (MCCF) eInsurance Compliance Phase 3 project related to Integrated Billing (IB). eInsurance provides Insurance identification and verification which is vital to the success of the Department of Veterans Affairs (VA) revenue collection process. Accurate insurance information is needed to effectively submit claims and collect payments from third-party payers for medical care and services provided to Veterans by the Veterans Health Administration (VHA). The following feature of the IB software will be affected by this project: The VistA software has been updated to re-evaluate the patient's current insurance coverage when they are identified in VistA as being deceased. Note, that if the date of death entered is TODAY or NOW or TODAY-1 then the 'COVERED BY HEALTH INSURANCE' field (#2,.3192) will remain at "Y" if they have an active policy on file, as the automated process associated with the 'DATE OF DEATH' field (#2,.351) would term that policy with the date of death+1. A term date of TODAY or NOW or TODAY+1 is considered an active policy when it is evaluated. Patch Components ================ Files & Fields Associated: File Name (#) New/Modified/ Sub-file Name (#) Field Name (Number) Deleted ------------------- --------------------------------- ------------- N/A Bulletins Associated: New/Modified/ Bulletin Name Deleted ------------- ------------- N/A Dialogs Associated: New/Modified/ Dialog Name Deleted ----------- ------------- N/A Forms Associated: New/Modified/ Form Name File Name (Number) Deleted --------- ------------------ ------------- N/A Functions Associated: New/Modified/ Function Name Deleted ------------- ------------- N/A HL Logical Link: New/Modified/ HL Logical Name Deleted --------------- ------------- N/A HL7 Application Parameters: New/Modified/ HL7 Parameter Name Deleted ------------------ ------------- N/A HLO Application Registry: New/Modified/ HLO Registry Name Deleted ----------------- ------------- N/A Help Frames Associated: New/Modified/ Help Frame Name Deleted --------------- ------------- N/A Mail Groups Associated: New/Modified/ Mail Group Name Deleted --------------- ------------- N/A Options Associated: New/Modified/ Option Name Type Deleted ----------- ---- ------------- N/A Parameter Definitions: New/Modified/ Parameter Name Deleted -------------- ------------- N/A Parameter Template: New/Modified/ Template Name Deleted ------------- ------------- N/A Protocols Associated: New/Modified/ Protocol Name Deleted ------------- ------------- N/A Remote Procedures Associated: New/Modified/ Remote Procedure Name Deleted --------------------- ------------- N/A Security Keys Associated: New/Modified/ Security Key Name Deleted ----------------- ------------- N/A Templates, Input Associated: New/Modified/ Template Name Type File Name (Number) Deleted ------------- ---- ------------------ ------------- N/A Templates, List Associated: New/Modified/ Template Name Type Deleted ------------- ---- ------------- N/A Templates, Print Associated: New/Modified/ Template Name Type File Name (Number) Deleted ------------- ---- ------------------ ------------- N/A Templates, Sort Associated: New/Modified/ Template Name Type File Name (Number) Deleted ------------- ---- ------------------ ------------- N/A Additional Information: ---------------------- N/A New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A Remedy Ticket(s) & Overview --------------------------- 1. Ticket #R11229286FY17 Inconsistent Data Elements report Problem: ------- As a result of automated processes in IB*2.0*549, when a patient is identified as deceased in VistA the patient's active policies are termed. However, the field 'COVERED BY HEALTH INSURANCE' (#2,.3192) is not updated to accurately reflect the proper status of the patient's insurance coverage. Resolution: ---------- The VistA software has been updated to re-evaluate the patient's current insurance coverage when they are identified in VistA as being deceased. Note, that if the date of death entered is TODAY or NOW or TODAY-1 then the 'COVERED BY HEALTH INSURANCE' field (#2,.3192) will remain at "Y" if they have an active policy on file, as the automated process associated with the 'DATE OF DEATH' field (#2,.351) would term that policy with the date of death+1. A term date of TODAY or NOW or TODAY+1 is considered an active policy when it is evaluated. Patient Safety Issues (PSIs) --------------------------------- N/A Defect Tracking System Ticket(s) & Overview --------------------------------------------------------- N/A Test Sites: ------------- VA Nebraska Western Iowa Health Care System Chillicothe VA Medical Center Documentation Retrieval Instructions --------------------------------------------- Updated documentation describing the new functionality introduced by this patch is available. The preferred method is to SFTP the files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve software directly from a specific server. Sites may retrieve the documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany domain.ext Hines domain.ext Salt Lake City domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ Title File Name FTP Mode ------ --------- -------- Release Notes/Installation Guide ib_2_0_p579_rn.pdf Binary Patch Installation: Pre/Post Installation Overview ------------------------------------- The installation of this patch may be QUEUED. To avoid disruptions, this patch should be installed during non-peak hours when there is minimal activity on the system and there are no Integrated Billing users on the system. Do not delete the post install routine "IBY579PO" after the install has been completed, as a task has been queued to run in the background and it needs this routine to complete. ******************************************************************** * You may want to rebuild the 'INCONSISTENT DATA' file (#38.5) * * 24 hours after IB*2.0*579 is installed. One may run/queue the * * option that is described below in the post installation * * instructions. * ******************************************************************** Pre-Installation Instructions ---------------------------------- ***************************************************************** * You should install this patch during non-peak hours, when no * * Integrated Billing users are on the system. * ***************************************************************** This patch may be installed with users on the system although it is *strongly* recommended that it be installed during non-peak hours to minimize potential disruption to users. This patch should take less than 5 minutes to install. Installation Instructions ----------------------------- 1. Choose the PackMan message containing this patch. 2. Choose the INSTALL/CHECK MESSAGE PackMan option. 3. From the Kernel Installation and Distribution System Menu, select the Installation Menu. When prompted for the INSTALL enter the patch #(ex. IB*2.0*579): 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. From the Installation Menu, select the Install Package(s) option and choose the patch to install. 5. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', enter NO. 6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', enter NO. 7. If prompted 'Delay Install (minutes): (0 - 60): 0//', respond 0. 8. When prompted 'Device: HOME//', respond with the correct device. Post-Installation Instructions ----------------------------------- IBY579PO does the following: Reviews all deceased patients in the system where the 'COVERED BY HEALTH INSURANCE' field (#2,.3192) has a value of 'Y'. The software evaluates whether or not the patient has active policies on file and sets the 'COVERED BY HEALTH INSURANCE' field appropriately. In order to verify the patch post-installation routine was run successfully, please examine the Install File for this patch and report any error messages to Product Support. ************************************************************* * VERY IMPORTANT * * -------------- * * * * If you would like to remove the false reporting of the * * inconsistency 'INSURANCE YES BUT NONE ACTIVE' from the * * option, 'Inconsistency Data Elements Report' [DG * * CONSISTENCY PRINT] you must rebuild the 'INCONSISTENT * * DATA' file (#38.5) 24 hours after IB*2.0*579 is * * installed. Please refer to the 'User Manual - Supervisor * * ADT Menu' on the VistA Database Library (VDL) under the * * Clinical section, category 'Admission Discharge Transfer' * * to learn about the option 'Rebuild Inconsistency File' * * [DG CONSISTENCY REBUILD], which may be queued. * * * * DO NOT rebuild the file within 24 hours of installing * * this patch as it would change nothing on your system and * * the false reporting would still exist on your report. * ************************************************************* Routine Information: ==================== The second line of each of these routines now looks like: ;;2.0;INTEGRATED BILLING;**[Patch List]**;21-MAR-94;Build 2 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: IBCNEUT7 Before: B72027534 After: B79064178 **184,549,579** Routine Name: IBY579PO Before: n/a After: B36838238 **579** Routine list of preceding patches: 549 ============================================================================= User Information: Entered By : Date Entered : OCT 27, 2016 Completed By: Date Completed: DEC 15, 2016 Released By : Date Released : DEC 19, 2016 ============================================================================= Packman Mail Message: ===================== $END TXT