============================================================================= Run Date: MAY 23, 2022 Designation: EAS*1*212 Package : EAS - ENROLLMENT APPLICATION SYSTEM Priority: Mandatory Version : 1 SEQ #183 Status: Released Compliance Date: JUN 23, 2022 ============================================================================= Subject: VHA ENROLLMENT SYSTEM (VES) 6.1 RELEASE Category: - Informational Description: ============ The purpose of this informational patch description is to announce the release of the Veterans Health Administration (VHA) Enrollment System (VES) 6.1. This release, developed in Java technology, contains Eligibility and Enrollment (E&E) development and upgrade efforts. This release includes enhancements and defect fixes to support Enrollment System Modernization (ESM), Enrollment System Community Care (ESCC) and VES Sustainment. VES 6.1 was successfully deployed on Saturday, May 21, 2022. The following functionality is updated in this VES 6.1 release: 1. VES is enhanced to allow users to easily identify Veterans and non- Veterans who are eligible for the Housing and Urban Development-Veterans Affairs Supportive Housing (HUD-VASH) program. a. A new non-Veteran Eligibility Code, "HUD-VASH", is added to the Eligibility tab. b. Eligibility tab rules for Ineligible Reasons and Pending Verification / Re-Verification Reasons are updated for HUD-VASH: When the user selects "Yes" for the HUD-VASH Non-Veteran Eligibility Code but the Ineligible Reason or Pending Verification / Re-Verification Code is one that doesn't qualify for HUD-VASH, VES displays an error message informing the user that HUD-VASH cannot be selected and informs the user of the currently assigned Ineligible Reason or Pending Verification / Re-Verification Reason Code. c. VES assigns the HUD-VASH Secondary Eligibility and VHA Profile (VHAP) as follows: i. When the HUD-VASH Non-Veteran Eligibility Code is by default set to "No", the person's record will NOT have a Secondary Eligibility of "HUD-VASH" or a VHAP of "HUD-VASH Restricted Care" assigned. ii. When a user sets the HUD-VASH Non-Veteran Eligibility Code to "Yes": - A HUD-VASH qualifying person's record is saved successfully upon selection of the "Accept Changes" button. - VES assigns the Secondary Eligibility of "HUD-VASH" in addition to the Primary and Secondary Eligibilities as determined by the rules for the data conditions of the current record. - The new VHAP "HUD-VASH Restricted Care" is assigned in addition to the Core and Carveout VHAPs as determined by the rules for the data conditions of the current record. iii. When a user manually sets the HUD-VASH Non-Veteran Eligibility Code from "Yes" to "No", a HUD-VASH qualifying person's record is saved successfully upon selection of the "Accept Changes" button. - VES only removes the currently assigned Secondary Eligibility of "HUD-VASH". - VES only removes the currently assigned Carveout VHAP "HUD- VASH Restricted Care". d. VES is updated to send and receive the HUD-VASH Secondary Eligibility Code and VHAP to and from VistA. i. When a VistA user removes HUD-VASH from a former servicemember's record after they have completed the HUD-VASH program, the HUD-VASH assignment is removed from VES for the same person. ii. When VES receives a Secondary Eligibility Code of HUD-VASH from VistA: - If the person's record in VES qualifies for HUD-VASH, the HUD-VASH Secondary Eligibility and the corresponding VHAP are assigned in VES. - If the person's record in VES does not qualify for HUD-VASH, either through a non-qualifying Ineligible Reason Code or non-qualifying Pending Verification / Re-Verification Reason, the HUD-VASH Secondary Eligibility and the corresponding VHAP are NOT assigned in VES and no work item is created. VES will send a Health Level Seven (HL7) ORU/ORF-Z11 message to VistA to remove the HUD-VASH eligibility. - If the person's record in VES is either missing the Ineligible Reason Code or the Pending Verification / Re- Verification Reason and VES is unable to determine if HUD- VASH can be assigned or not, then a work item is created. e. The "SDS Eligibility_Code" table in the Standard Data Service (SDS) database is updated with the new HUD-VASH Secondary Eligibility Code. f. In order to share updates with VistA sites where the person is known, records are seeded for HUD-VASH Secondary Eligibility assignments. 2. VES is updated to query the Corporate Data Warehouse (CDW) for additional hardship reasons that were added with Consult Toolbox (CTB) 2.0. This will allow VES to have the latest consult factors for a hardship and assign the proper Veterans Choice Eligibility (VCE) value and VHAP. Upon receiving the new consult factors successfully, VES assigns the following to the record: a. VCE - Hardship (H) b. VHAP - Veteran Plan CCP Hardship Determination (CCP H) 3. VES is updated to include all Ineligible Reason Codes and Military Service Episode Data to the OIT Homeless Program Report Extracts. Updating this functionality will result in Veterans receiving the appropriate eligibility determinations for VA Homeless programs. 4. VES is updated to include the Community Care (CC) hardship expiration date on the E&E web service so that it can be available to subscribers. 5. VES, which currently locks inactive accounts after a one-year period, will now lock accounts after 90 days of inactivity to comply with Federal Information Security Management Act (FISMA) requirements. VES will send a reminder email to users 7 days prior to their account being locked. 6. The VES database is updated to include 5 new letters (Creditable Coverage Letter, Special Eligibility Proof Request, Registration Only Letter, Returned Mail Letter and Caregiver Letter). These letters will not be able to be triggered from VES until a future release. VES Sustainment Defect Fixes Included in VES 6.1: VES-19278 Enrollment history calls on inbound data work manager transactions are sticking, causing the transactions to delay and be redelivered by the Java Transaction Application Programming Interface (JTA) VES-21618 VES is not processing the relationship "Aunt" from Cerner VES-22179 After Future Discharge Date (FDD) maturity is reached and the FDD batch job is executed, the VBA Query status remains in "Pending Response" 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: -------- --------------------- VES-19278 Problem: Enrollment history calls on inbound data work manager transactions are sticking, causing the transactions to delay and be redelivered by the JTA. Resolution: Removed enrollment history calls for rules that don't need them and modified the rule for "ProcessLetterSendRequest" so that it functions properly. VES-21618 Problem: VES is not processing the relationship "Aunt" from Cerner. Resolution: Updated mapping for the inbound relationship value from Cerner so that all relationships are properly processed. VES-22179 Problem: After FDD maturity is reached and the FDD batch job is executed, the VBA Query status remains in "Pending Response". Resolution: Modified code so that the status of the VBA Query is updated properly instead of remaining in "Pending Response". 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 ------------------------------------------------------------ VES 6.1 Release Notes VES_6_1_RN.PDF VES 6.1 User Guide VES_6_1_UG.PDF Patch Installation: ES will be installed at Amazon Web Services (AWS). ****** 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 AWS 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 : DEC 28, 2021 Completed By: Date Completed: MAY 23, 2022 Released By : Date Released : MAY 23, 2022 ============================================================================= Packman Mail Message: ===================== No routines included