============================================================================= Run Date: MAY 24, 2021 Designation: EAS*1*199 Package : EAS - ENROLLMENT APPLICATION SYSTEM Priority: Mandatory Version : 1 SEQ #171 Status: Released Compliance Date: JUN 24, 2021 ============================================================================= Subject: ENROLLMENT SYSTEM (ES) 5.16 RELEASE Category: - Informational Description: ============ The purpose of this informational patch description is to announce the release of the Enrollment System (ES) 5.16. This release, developed in Java technology, contains Enrollment System Modernization (ESM) Phase 3 development and upgrade efforts. This release includes enhancements and defect fixes to support Enrollment System Community Care (ESCC), Electronic Health Record Modernization (EHRM), and ES Sustainment. ES 5.16 was successfully deployed on Saturday, May 22, 2021. ************************************************************************** Please note that since VA support for Internet Explorer (IE) will be phased out by August 2021, we recommend using either the Chrome or Edge browser to access the context-sensitive ES Online Help starting with ES version 5.16. Alternatively, users may either: - Access the general ES Online Help at the following URL in IE: https://vaww.esr.aac.domain.ext/esr/webhelp/esr_help_project.htm#t= online_help%2Fenrollment_system.html, or - Access the ES User Guide on the VA Software Document Library: https://www.domain.ext/vdl/ ************************************************************************** The following functionality is updated in this ES 5.16 release: Enrollment System Modernization (ESM) 1. ES is updated to include a comment field in the Community Care Network (CCN) message log so that administrators and specified users can view that an error has been resolved and/or dispositioned. a. A new "Edit CCN Log User Comments" capability controls whether a user can enter and/or edit a comment on the CCN message log. b. ES includes a "Comments" column on each row of the CCN message log results regardless of message status. c. For users with the new "Edit CCN Log User Comments" capability, an "Add/Edit" link is displayed on each row. d. Upon clicking the "Add/Edit" link, a screen is displayed that allows the user to add a new comment or edit any existing comments. 2. The Enrollment System and VistA currently assign the "Not Eligible; Ineligible Date" status after the "REGISTRATION ONLY" status which does not properly reflect the enrollment status for ineligible Non- Veterans. With ES 5.16, the system is updated to override the enrollment statuses of "Not Applicable" and "REGISTRATION ONLY" with "Not Eligible; Ineligible Date" when ineligibility fields are populated. ES will assign the Enrollment Status field the value of "Not Eligible; Ineligible Date" regardless of the answer to Do You Wish to Enroll? whenever an ineligible date and reason are populated. a. The system is modified to enable the Ineligible Date, Ineligible Reason, and Ineligible VARO Decision fields to be populated when the enrollment status is "REGISTRATION ONLY". b. ES is modified to disable the Ineligible Date field(s) during the Add A Person (AAP) process; this will prevent users from entering ineligibility information without completing the record. c. ES is modified to update Determine VHA Profile rules Decision 50, Non-Veteran Other Restricted Med Benefits for ineligible Veterans to include the Enrollment Status of "Not Eligible; Ineligible Date" when a record has mental health care (MH Care) and an ineligible date. ************************************************************************** NOTE: To ensure that the correct Enrollment Status is reflected in patient records, it is recommended to only enter/update the Ineligible Date and Reason in ES until DG*5.3*1045 is installed in the VistA production environment. ************************************************************************** 3. ES is updated to no longer execute the WebHINQ batch job that processes VBA data sent to ES from eGate, which is unsupported and needs to be decommissioned. Instead, when requesting VBA data for a Veteran, ES will queue requests to query the VA Profile Services for that Veteran. a. The button to query the MSDS Broker on the Military Service tab is updated to "Query VBA and MSDS Data". b. The confirmation page title is changed to "Query VBA and MSDS Data" and the screen heading is changed to "Query VBA and MSDS Data Message Confirmation". c. If the user selects "Confirm", ES will queue a request to query the VA Profile Service and MSDS for that Veteran, direct the user back to the originating screen, and display the updated confirmation message "The Query VBA and MSDS Data Message has successfully been added to the queue of messages to be sent." 4. The ES eligibility rules under the "Grandfather" provision of the MISSION Act of 2018 (VA Maintaining Systems and Strengthening Integrated Outside Networks Act) are modified to no longer consider distance data for Veterans who were included in the initial Community Care Grandfathered population and live in one of the five lowest populated density states (AK, MT, ND, SD, WY). These Veterans will be assigned Grandfather eligibility (VCE G) without sending their record to the Geographer Support Services Center (GSSC) (formally known as Planning Systems Support Group (PSSG)) going forward; however, ES will continue to share their Community Care eligibility information with downstream systems/processes. In addition, this enhancement will support the VHA Support Service Center (VSSC) effort to sunset the monthly Veterans Access Choice and Accountability Act of 2014 (VACAA) Report. a. ES is modified to relax Grandfather eligibility (VCE-G) rules to no longer evaluate mileage for Veterans included in the initial Grandfathered population (those who were eligible for and assigned a Grandfathered VCE pursuant to the MISSION Act on June 6, 2019). Newly enrolled Veterans who live in one of the five lowest population density states do not qualify for a Community Care outcome that includes Grandfathered. b. ES is modified to relax State with No Full-Service Medical Facility eligibility (VCE-N) rules to remove White River Junction VAMC and mileage criteria for Veterans residing in New Hampshire. c. ES is modified to recalculate the Community Care outcome when a Veteran included in the initial Grandfathered population changes their Residential Address. i. From a low population density state to a state that is not a low population density state (remove Grandfathered outcome), or ii. From a state that is not in low population density state to a low population density state (regain Grandfathered outcome). d. ES is modified to exclude Veterans who were included in the initial Grandfathered population when sharing records with GSSC for the purpose of determining distance data based on Choice rules. e. The Community Care Determination page is modified: i. Each sub-panel displays horizontally from left to right margins. ii. The header displays the "VIEW GEOCODE TRANSMIT HISTORY" link. iii. Veteran Information headers display the links "SEND TO CONTRACTORS", "View Data Sent to CCN Contractors", and "View Data Sent to TPA." f. The field label "Residential Address at the time of Drive Distance Determination" is shortened to "Residential Address". g. The Community Care Outcome panel is modified to align and display the Override arrows, labels, and radio buttons on the same line for each. h. ES is modified to display only the relevant header rows when the geocoding date is after ES release 5.16 and both previous and current values are blank. i. ES is modified to display blanks in the "New Value" column in all fields for previously Grandfathered Veterans when geocoding date is after ES release 5.16 and an old value exists on the History Change Details record in one or both of the following sections: i. Veteran Information ii. Nearest VAMC Facility j. ES is modified to display blanks in the Geocoding Result and Driving Distance columns on the Eligibility -> Geocode Transmit History page when geocoding date is after ES release 5.16. i. Both these columns will continue to have data in the Administrative Data Repository (ADR) database. ii. The PSSG ETL process will continue to detect changes in driving distance and trigger VCE recalculations. This will not affect the eligibility outcome. iii. The ETL process will also continue to generate record counts that are part of ESCC Quality email, which is no longer required. k. The ESCC Quality Report is modified to remove the following sections: i. Discrepancy between Residential Address and Geocoding ii. PSSG iii. Reconciliation Process for Title-38 Care Received for Grandfather VCE (CDW) Electronic Health Record Modernization (EHRM) 1. Currently, when an ES user adds an address during the Add A Person functionality, the system forces the user to enter one address at a time, despite the fact that the Mailing Address (MA) and the Residential Address (RA) are usually the same address. With this release, ES is updated so that the ES user will be able to enter either MA or RA and be able to click a button or check a box to automatically update the other address. a. A new checkbox with the label "Save to Mailing Address?" is added to the address entry screen when adding or updating a Residential Address. b. A new checkbox with label "Save to Residential Address?" is added to the address entry screen when adding or updating a Mailing Address. c. When the address screen is initially rendered, the checkbox is unchecked. d. A physical address (i.e., no P.O. Box or General Delivery) must be entered for the Mailing Address when the "Save to Residential Address?" indicator is selected, or a warning message is displayed. e. When a user is attempting to complete a registration, ES will verify that a Residential Address has been entered and, if not, display the error "Residential Address is required". 2. ES is updated to change the label "Permanent Mailing Address" to "Mailing Address" wherever it appears. 3. ES is updated to add a new Service Branch for "Space Force" to capture military service information for those in the new military service branch of US Space Force. a. ES interfaces now recognize Space Force when sending and receiving messages. b. ES users are able to add/edit/delete a military service episode with a Service Branch of Space Force per existing rules. Operational Decision Manager (ODM) Under ODM, the 71 iLOG rule sets were transferred from iLOG to ODM. A Mediation Framework was established to allow the system administrators to switch between the iLOG and ODM rules sets as the rules sets are integrated into the ES application. Once the migration is fully completed to ODM, the rules will not be switched back to iLOG unless there is a systemic issue with ODM. ES 5.16 supports integration of the Process IVM Financials rule set. ES Production Defect Fixes VES-12455 An error message is displayed when selecting any POW camp in the Prisoner of War section on the Person Search > Eligibility > Eligibility Edit page. VES-12666 VHAP should be recalculated when "RxCopay" expires after 365 days. VES-12676 At the Cerner site, service-connected disabilities are displaying in a single line and are difficult to read. VES-12677 "StackOverflow" errors occur on model properties recursion. VES-13970 The "AssociationValidation" rule is throwing an exception in the rules log. ES Sustainment Defect Fixes VES-9560 Repeated DGEN bulletins for ineligible records. VES-10145 Section 508: Information, structure, and relationships conveyed through presentation cannot be understood (programmatically determined). VES-10146 Section 508: When input errors are automatically detected, the item that is in error is not identified and described to the user in text. VES-10148 Section 508: The name, role, state or value of user interface elements in the product cannot be understood (programmatically determined). VES-10205 Home Phone # is getting stored in the Address table when the phone number is entered from the Search/Add screen. VES-12079 Fortify: On line 768 of HistoryDAOImpl.java, execute() uses hibernate to execute a dynamic SQL statement built with input coming from an untrusted source. VES-12084 Fortify: Null Dereference and Portability Flaw: Locale Dependent Comparison. VES-12234 Clean-up old Enrollment and Eligibility (E&E) Service code. VES-12259 Identical duplicate rows are inserted into the Enrollment Application Table when a user starts the Add A Person process. VES-12337 The CCN daily batch process is experiencing latency issues. VES-12904 The Programmable Logic Controller (PLC) letter extract is missing required fields. VES-13402 "PersonTraits" needs to be excluded from hibernate optimistic locking checks as the updates are asynchronous. VES-13836 Automation: Uncaught reference error: "addAlertText" is not defined on adding a person using Python automation tool. VES-14152 A feedback loop is occurring on inbound Health Benefit updates. VES-14419 ES is not correctly evaluating the existence of the Patient Identity (PI) active correlation upon completing registration in the proxy add step to VistA. Patch Components: ----------------- N/A Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ --------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- Additional Information: New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: Jira: Bug # Problem / Resolution: -------- --------------------- ES Production: VES-12455 Problem: An error message is displayed when selecting any POW camp in the Prisoner of War section on the Person Search > Eligibility > Eligibility Edit page. Resolution: Updated backend JavaScript to correct the error. VES-12666 Problem: VHAP should be recalculated when "RxCopay" expires after 365 days. Resolution: Added a daily batch job that will recalculate the VHAP for records with expired Rx tests. VES-12676 Problem: At the Cerner site, service-connected disabilities are displaying in a single line and are difficult to read. Resolution: Updated code to properly display rated disabilities. VES-12677 Problem: "StackOverflow" errors occur on model properties recursion. Resolution: Updated model properties for "DocumentAudit" to prevent stack overflow. VES-13970 Problem: The "AssociationValidation" rule is throwing an exception in the rules log. Resolution: Updated code to avoid log errors for association validation rule. ES Sustainment: VES-9560 Problem: Repeated DGEN bulletins for ineligible records. Resolution: Modified code to check on Veteran indicator. VES-10145 Problem: Section 508: Information, structure, and relationships conveyed through presentation cannot be understood (programmatically determined). Resolution: Modified code in the affected screens to move the focus from "Skip to Main Content" to the first item/field of the page. VES-10146 Problem: Section 508: When input errors are automatically detected, the item that is in error is not identified and described to the user in text. Resolution: Modified code on the affected screens to add audio indication when a user tries to type in more than the maximum allowed characters and the characters do not appear on the screen. VES-10148 Problem: Section 508: The name, role, state or value of user interface elements in the product cannot be understood (programmatically determined). Resolution: Modified code so that assistive technology will read name, state, role, and value when an expandable section is expanded or collapsed. VES-10205 Problem: Home Phone # is getting stored in the Address table when the phone number is entered from the Search/Add screen. Resolution: Commented out code to keep the phone number from being added to the address table. VES-12079 Problem: Fortify: On line 768 of HistoryDAOImpl.java, execute() uses hibernate to execute a dynamic SQL statement built with input coming from an untrusted source. Resolution: Analysis found that this finding is a false positive; no code changes are required. VES-12084 Problem: Fortify: Null Dereference and Portability Flaw: Locale Dependent Comparison. Resolution: Made minor changes in the code to resolve the null dereference and portability problems. VES-12234 Problem: Clean-up old Enrollment and Eligibility (E&E) Service code. Resolution: Cleaned up the "HECMS-websrv" project to remove the old E&E Service code. VES-12259 Problem: Identical duplicate rows are inserted into the Enrollment Application Table when a user starts the Add A Person process. Resolution: Updated code to no longer create duplicate entries in the database. VES-12337 Problem: The CCN daily batch process is experiencing latency issues. Resolution: Updated CCN daily batch process to include all acquired data from the query. VES-12904 Problem: The Programmable Logic Controller (PLC) letter extract is missing required fields. Resolution: Modified the retrieval of the Initial Pending Notification (IPN) date method for closure letters. VES-13402 Problem: "PersonTraits" needs to be excluded from hibernate optimistic locking checks as the updates are asynchronous. Resolution: Updated code to remove versioning from the "PersonTraits" hibernate mapping file. VES-13836 Problem: Automation: Uncaught reference error: "addAlertText" is not defined on adding a person using Python automation tool. Resolution: Added "addAlertText" function to the "ESR-Script.js" JavaScript and removed that function from Java Server Pages (JSP). VES-14152 Problem: A feedback loop is occurring on inbound Health Benefit updates. Resolution: Updated code to prevent Add a Person creation and feedback loop through inbound EHRM updates. VES-14419 Problem: ES is not correctly evaluating the existence of the Patient Identity (PI) active correlation upon completing registration in the proxy add step to VistA. Resolution: Added PI check to the match criteria for "correlation exists". Test Sites: ----------- Health Eligibility Center (HEC) Software and Documentation Retrieval Instructions: -------------------------------------------------- Documentation describing the new functionality is included in this release. Documentation can be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/. Documentation can also be obtained at https://download.vista.domain.ext/index.html/SOFTWARE. Documentation Title File Name ------------------------------------------------------------ ES 5.16 Release Notes ES_5_16_RN.PDF ES 5.16 User Guide ES_5_16_UG.PDF Patch Installation: ES will be installed at the Austin Information Technology Center (AITC). ****** This is an informational patch ONLY. ****** ****** There is NO install to be done by sites. ****** Pre/Post Installation Overview: ------------------------------- N/A Pre-Installation Instructions: ------------------------------ N/A Installation Instructions: -------------------------- ES will be installed at the AITC only. ****** This is an informational patch ONLY. ****** ****** There is NO install to be done by sites. ****** Post-Installation Instructions: ------------------------------- N/A Back-Out/Roll Back Plan: ------------------------ N/A Routine Information: ==================== No routines included. ============================================================================= User Information: Entered By : Date Entered : FEB 17, 2021 Completed By: Date Completed: MAY 24, 2021 Released By : Date Released : MAY 24, 2021 ============================================================================= Packman Mail Message: ===================== No routines included