============================================================================= Run Date: NOV 23, 2020 Designation: EAS*1*194 Package : EAS - ENROLLMENT APPLICATION SYSTEM Priority: Mandatory Version : 1 SEQ #165 Status: Released Compliance Date: DEC 24, 2020 ============================================================================= Subject: ENROLLMENT SYSTEM (ES) 5.14 RELEASE Category: - Informational Description: ============ The purpose of this informational patch description is to announce the release of the Enrollment System (ES) 5.14. 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.14 was successfully deployed on Saturday, November 21, 2020. The following functionality is updated in this ES 5.14 release: Enrollment System Modernization (ESM) 1. ES is enhanced to include a new document type of Income Verification Division (IVD) within the Document Management functionality. Currently, there is no document management system to manage Income Verification correspondence received from Veterans. As a result, Income Verification staff at the Health Eligibility Center (HEC) are physically handling 400k-500k+ paper documents annually. Implementation of this enhancement will reduce storage and resource costs, reduce delays in adjudicating cases and support timely notifications to Veterans. This enhancement also provides an audit trail and allows for timely responses to Congressional inquiries. 2. Sets of deactivated records exist in the ES Administrative Data Repository (ADR) database. ES currently does not alert users that a record is deactivated. ES is enhanced to alert users when a record is deactivated and provides a hyperlink to the active record. 3. In ES 5.13, ES was enhanced to disable the three Assets fields ("Cash and Bank Account Balance", "Land, Buildings Less Mortgage and Liens", and "Other Property or Assets") on the Edit Financials Information screen. Removing user entry for the three Assets fields prevented the supplemental adjudication question from being presented, as it is no longer required as part of the financial assessment process. With ES 5.14, the system is enhanced to also disable the Assets fields on the Edit Financial Details screen. Electronic Health Record Modernization (EHRM) 1. ES is enhanced to provide identification of the originating source system for all contact information changes. This change will allow all contact information exceptions to be assigned to the VA Medical Center (VAMC) that made the error to resolve the errors. This provides the required provenance for accountability, reporting, and needed education activities to further improve VA contact information for our VA customers. 2. ES and VistA were updated in the 5.12 and 5.13 releases to allow Veterans a choice of either "Enrolling" with the Veterans Health Administration (VHA) or completing a "Registration" only. The initial requirement only allowed the Veteran to change this answer from No to Yes, but not from Yes to No if a mistake was made. Also, the Enrollment System currently sets Non-Veteran records with a date of death to a "Not Applicable" enrollment status instead of the expected "Deceased" enrollment status. a. ES is enhanced to allow users to change the answer of the "Do You Wish To Enroll" question from Yes to No in case a mistake is made during the initial registration. b. A new capability titled "Edit Registration Option" is added to ES. Only users with this capability are able to change the answer of the "Do You Wish To Enroll" question from Yes to No. c. ES is enhanced to set Non-Veteran records to an enrollment status of Deceased when a date of death is entered or received. d. When a record is in an enrollment status of Cancelled/Declined, the system allows users with the "Edit Registration Option" capability to change the answer of "Do You Wish To Enroll" from Yes to No, but does not allow the user to set the value to "No Data". The "No Data" option is disabled once "Do You Wish To Enroll" has been initially set to either "Yes" or "No". e. Once a user changes the answer of "Do You Wish To Enroll" from Yes to No, ES requires the user to enter the "Self-Reported Registration Only Reason" on the Edit Current Eligibility panel on the Eligibility tab. f. ES displays a new confirmation popup when a user sets the "Do You Wish To Enroll" question to Yes. g. The confirmation popup is displayed for all new records (Blank to Yes) and for existing records (No to Yes). h. ES displays a new canceled/declined reason of "Erroneous Enrollment due to Clerical Error". The "Source of Registration" field will remain populated when enrolling in ES on a point- forward basis. i. ES will not send the cancelled/declined letter (742-620A - Cancel/Decline Enrollment Letter) when a canceled/declined reason of "Erroneous Enrollment due to Clerical Error" is entered. j. The existing "Reason Cancel/Declined Not Processed" label on the Person Search > Enrollment page is updated to display "Reason Canceled/Declined Not Processed". k. ES is updated to store the "Source of Registration" when the answer to "Do You Wish To Enroll" is set to Yes. l. The "Source of Registration" field will remain populated when enrolling in ES on a point-forward basis. m. When adding a date of death to a non-Veteran record, ES sets the enrollment status to "Deceased". n. ES will complete a cleanup job that will identify all non-Veteran records with a date of death and update them to an enrollment status of "Deceased". 3. VA Profile has not implemented Temporary Address as no other Line of Business (LOB) in VA uses a Temporary Address. Cerner implementation does not support the use of Temporary Address; only addresses for Permanent Mailing Address and Residential Address flow from VistA to ES and ES to VA Profile to Cerner. If a Temporary Address is used at a Cerner-enabled site, mail could be misdirected to that address and not the Permanent Mailing Address or Residential Address. The functionality for ES to eliminate the use of Temporary Address was developed and will be made available in a future release after the functionality is implemented in VistA. 4. ES currently supports twelve phone type options and is changing to support the same values in the Phone Type dropdown list as interfacing partners enterprise wide. ES has reduced the number of options in the dropdown list displayed on the Demographics Addresses tab to match valid values in the Cerner application as of the date of this release. ES limits the Phone Type dropdown list to the following selectable options: a. Home b. Cell/Mobile c. Work d. Temporary (Temporary phone numbers will continue to display until this functionality is removed from VistA and the ES system parameter is set to "N") 5. ES is enhanced to include Emergency Response Indicators (ERIs) and associated data in the Enrollment and Eligibility (E&E) Web Service. VA Profile requires ERI values and historical information from the authoritative source (ES), so that individuals receiving VA care due to a public health crisis can be properly identified. 6. ES is enhanced to store and display an updated description for the Veteran Plan CCP Restricted Care VHAP. 7. ES has been updated to capture Community Care hardships that are entered from Cerner Millennium so that the Veteran Hardship Veterans Choice Eligibility (VCE) can be updated and reflected in ES, as well as shared with downstream applications and partners. ES Production Defect Fixes: VES-603 Deleting the Mobile (Cell) Phone in VistA does not delete the Mobile (Cell) phone in VA Profile. VES-1358 Duplicates are sent in the Community Care Network (CCN) daily file. VES-1534 The count of VHA Profiles under the "New Value" column on the View Historical Eligibility Screen is incorrect after the Veteran indicator was changed to "No" and an Ineligible Date was entered. VES-2298 Section 508: Associate Foreign Address. VES-6116 Deleting the Home Phone in VistA does not also delete the Home Phone in ES (if ES has multiple phones). VES-6704 A JavaScript Error is occurring on the Agreement modal load in Staging. VES-6974 ES is displaying both Code and Description for "Site of Change". VES-8166 Notification was not sent to VA Profile when there was an update in SW Asia condition. VES-8167 Open work items were created in ES for a Newborn Non-Veteran record with the message "Military Service Data (MSDS Query Blocked - Identity Traits Missing)". VES-9141 New VCEs for Collaterals and Covered Veterans need to be added to the VCE counts section of the ESCC Email Report. VES-9169 Database/User Interface displays "VIET NAM" instead of "VIETNAM" in the Country dropdown. VES-9361 Removing and adding the same Community Care Plan (CCP) with the same Effective Date in VistA is causing the ZCE segments to be out of sync with ES. VES-9399 The CCN Daily count reported in the ESCC Email Report is incorrect when the CCN batch process is still in process. VES-9413 Updating the Mobile (Cell) Phone in VistA is displaying a date/time related error in VA Profile. VES-9859 IVD Document Management: No validation error message is being displayed when a user performs an invalid date search. VES-9949 ESCC Quality Email Report: "VMBP" needs to be updated to "VHAP". ES Sustainment Defect Fixes: VES-546 Browser Compatibility - Chrome and Edge - Truncated text on various buttons in ES screens. VES-588 A null pointer exception was found in ES version 5.8. VES-590 ES did not trigger IVM migration upon change from Priority Group 8G to 8D. VES-598 VBA push to ES updates new eligibility date even though the eligibility status is not changed. VES-601 Net Income is not calculating for Copay Tests received from VistA. VES-618 ES does not deactivate temporary address when "No" is answered to the VistA prompt to delete. answers No to delete. VES-622 ES is transmitting two outbound messages to the same site for the same Veteran (using a deprecated data file number (DFN)). VES-647 Person Merge Fails if Veteran has Camp Lejeune eligibility. VES-1366 State Codes AA, AE, AP do not allow Box number for a Residential Address. VES-1394 Inbound addresses pushed from VA Profile are being added to empty/locked enrollment records. VES-4126 Browser Compatibility: VHIC button is not greyed out in Chrome. VES-6698 5.13.0 Fortify: Null Dereference. VES-6699 5.13.0 Fortify: Log Forging. VES-6700 5.13.0 Fortify: Unreleased Resource: Streams. VES-7055 ES is producing outbound Health Level 7 (HL7) messages to 200CRNR because that station was added as a type of VA Medical Center (VAMC); the messages are piling up in HealthConnect. VES-7081 5.13.0 Fortify: Password Management - 16 issues. VES-7144 When the VCE recalculation job updates a record that has both a traits change and a VCE change, it intermittently creates two separate entries to send to the Community Care Network (CCN) with different VCE statuses for the same person in the same file. VES-7155 Veteran Medical Benefit Plan (VMBP)/VCE jobs are creating brand new enrollment records in an invalid status for the surviving side of a duplicate/linked/merged record when the deprecated person is the one flagged for recalculation. VES-8259 Phone fields are being intermittently populated as false in the contact information adapter outbound to VA Profile. ES does not store these fields and always should be setting them as null instead of any Boolean value. VES-9197 5.14.0 Fortify: JSON Injection - 1 Issue - Unvalidated input is being written into JavaScript Object Notation (JSON). This call could allow an attacker to inject arbitrary elements or attributes into the JSON entity. VES-9199 5.14.0 Fortify: Privacy Violation - 3 issues. VES-9202 5.14.0 Fortify: Privacy Violation - 8 issues. VES-9204 5.14.0 Fortify: Race Condition: Singleton Member Field - 7 issues. VES-9273 5.14.0 Fortify: Weak Extensible Markup Language (XML) Schema: Unbounded Occurrences - 50 issues. VES-9379 Section 508: Focusable components in the content do not receive focus in an order that preserves meaning and operability. VES-9496 E&E Service: Schema validation is failing for an Income Verification Match (IVM) request. VES-9578 The "Send IVMUpdates" request in the E&E Service is throwing a Jakarta XML Binding (JAXB) unmarshalling exception error. VES-9581 E&E Service time stamp is different in new schema than in old schema. VES-9715 E&E Service missing policy effective date tag in new schema. VES-9932 Bidirectional Text (BIDI): Priority Group is not updated in ES on IVM conversion; Income Effective Date is removed in ES. VES-9959 E&E Service: "SendIVMUpdates" tag name in new service response is not matching the old service. VES-9962 E&E Service: Extra tag is displaying in "retrieveIVMCandidates" response in the new service. VES-10175 Military service changes are being sent to VA Profile when the record is not actually changed; this causes unnecessary messaging and creation of duplicate work items in Cerner Millennium. 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-603 Problem: Deleting the Mobile (Cell) Phone in VistA does not delete the Mobile (Cell) phone in VA Profile. Resolution: Updated code so that when a Cell Phone is deleted in VistA, the Cell Phone is also deleted in VA Profile. VES-1358 Problem: Duplicates are sent in the Community Care Network (CCN) daily file. Resolution: Modified the CCN batch process to send current data so that duplicate entries are no longer created. VES-1534 Problem: The count of VHA Profiles under the "New Value" column on the View Historical Eligibility Screen is incorrect after the Veteran indicator was changed to "No" and an Ineligible Date was entered. Resolution: Updated the screen to no longer display VHA Profiles and the count. VES-2298 Problem: Section 508: Associate Foreign Address. Resolution: Analysis found that the Section 508 issues reported were only occurring with the Automatic Reader in Job Access With Speech (JAWS); no coding changes needed. VES-6116 Problem: Deleting the Home Phone in VistA does not also delete the Home Phone in ES (if ES has multiple phones). Resolution: Analysis found that ES works as expected based on when the delete phone number comes from VistA; ES will not delete the phone number but will send the update to VA Profile. Upon receiving back the delete response from VA Profile, ES will delete the phone number. VES-6704 Problem: A JavaScript Error is occurring on the Agreement modal load in Staging. Resolution: Updated JavaScript to correct the error. VES-6974 Problem: ES is displaying both Code and Description for "Site of Change". Resolution: Updated code so that when the Code and Description are the same for "Site of Change", only the Code is returned. VES-8166 Problem: Notification was not sent to VA Profile when there was an update in SW Asia condition. Resolution: Added comparison code to check for updates in SW Asia condition so that the proper notification will be sent to VA Profile. VES-8167 Problem: Open work items were created in ES for a Newborn Non-Veteran record with the message "Military Service Data (MSDS Query Blocked - Identity Traits Missing)". Resolution: Removed the MSDS validation query for Social Security Number (SSN) required records. VES-9141 Problem: New VCEs for Collaterals and Covered Veterans need to be added to the VCE counts section of the ESCC Email Report. Resolution: Added the new VCEs to the ESCC Email Report. VES-9169 Problem: Database/User Interface displays "VIET NAM" instead of "VIETNAM" in the Country dropdown. Resolution: Updated Country dropdown to correctly display "VIETNAM". VES-9361 Problem: Removing and adding the same Community Care Plan (CCP) with the same Effective Date in VistA is causing the ZCE segments to be out of sync with ES. Resolution: Updated code so that the latest dates match and are in sync between ES and VistA. VES-9399 Problem: The CCN Daily count reported in the ESCC Email Report is incorrect when the CCN batch process is still in process. Resolution: Modified the stored procedure code so that if a count is not present, a text "CCN batch process not complete yet" is reported. VES-9413 Problem: Updating the Mobile (Cell) Phone in VistA is displaying a date/time related error in VA Profile. Resolution: Analysis found that this was a time zone issue between test accounts; no code change needed. VES-9859 Problem: IVD Document Management: No validation error message is being displayed when a user performs an invalid date search. Resolution: Updated code to display an error message when the user performs an invalid date search. VES-9949 Problem: ESCC Quality Email Report: "VMBP" needs to be updated to "VHAP". Resolution: Changed all instances of "VMBP" in the ESCC Quality Email Report to "VHAP". ES Sustainment: VES-546 Problem: Browser Compatibility - Chrome and Edge - Truncated text on various buttons in ES screens. Resolution: Updated code and formatting so that the button text no longer truncates. VES-588 Problem: ESM 5.8 PROD null pointer exception. Resolution: Updated messaging code to correct the null value. VES-590 Problem: ES did not trigger IVM migration upon change from Priority Group 8G to 8D. Resolution: Updated code to trigger IVM migration if a record moves from Priority Group 8G to any Enrolled Group. VES-598 Problem: VBA push to ES updates new eligibility date even though the eligibility status is not changed. Resolution: Updated rules to check current eligibility status. VES-601 Problem: Net Income not calculating for Copay Tests received from VistA. Resolution: Updated code so that Net Income and Threshold data displays in ES. VES-618 Problem: ES does not deactivate temporary address when VistA prompt answers No to delete. Resolution: Added rules for Temporary Address to the Operational Decision Manager (ODM) deploy list so that Temporary Addresses are synchronized. VES-622 Problem: ES is transmitting two outbound messages to the same site for the same Veteran (using a deprecated data file number (DFN)). Resolution: Updated code so that ES properly filters out deprecated DFNs from MVI correlation profiles. VES-647 Problem: Person Merge Fails if Veteran has Camp Lejeune eligibility. Resolution: Updated code and comments on Camp Lejeune so that the merge no longer fails and the user interface displays the merge page if there are comments. VES-1366 Problem: State Codes AA, AE, AP do not allow Box number for a Residential Address. Resolution: Updated code to exclude State Codes AA, AE, and AP from the rule blocking entry of Box numbers in Residential Address. VES-1394 Problem: Inbound addresses pushed from VA Profile are being added to empty/locked enrollment records. Resolution: Updated code to discard address updates for any record with no enrollment determination. VES-4126 Problem: Browser Compatibility: VHIC button is not greyed out in Chrome. Resolution: Updated style sheet so that the VHIC button is greyed out in Chrome and Edge browsers. VES-6698 Problem: 5.13.0 Fortify: Null Dereference. Resolution: Modified rules and code to no longer dereference a null pointer. VES-6699 Problem: 5.13.0 Fortify: Log Forging. Resolution: Updated code to correct the log forging issue. VES-6700 Problem: 5.13.0 Fortify: Unreleased Resource: Streams. Resolution: Updated code to release the resource. VES-7055 Problem: ES is producing outbound Health Level 7 (HL7) messages to 200CRNR because that station was added as a type of VAMC; the messages are piling up in HealthConnect. Resolution: Updated ES to filter out 200CRNR from the outbound builder since there is no VistA station to receive these messages. VES-7081 Problem: 5.13.0 Fortify: Password Management - 16 issues. Resolution: Analysis found that the affected configuration file is no longer used in Production. No code changes were necessary. VES-7144 Problem: When the VCE recalculation job updates a record that has both a traits change and a VCE change, it intermittently creates two separate entries to send to the CCN with different VCE statuses for the same person in the same file. Resolution: Modified the CCN batch process to send current data so that duplicate entries are no longer created. VES-7155 Problem: Veteran Medical Benefit Plan (VMBP)/VCE jobs are creating brand new enrollment records in an invalid status for the surviving side of a duplicate/linked/merged record when the deprecated person is the one flagged for recalculation. Resolution: Modified code so that ES will abandon the update if the record has no enrollment record yet. VES-8259 Problem: Phone fields are being intermittently populated as false in the contact information adapter outbound to VA Profile. ES does not store these fields and always should be setting them as null instead of any Boolean value. Resolution: Investigation found that there are not any phone entries with a value that directly came from ES. MPI identity transactions are updating the ES phone fields in the VA Profile phone table. No code changes were necessary. VES-9197 Problem: 5.14.0 Fortify: JSON Injection - 1 Issue - Unvalidated input is being written into JavaScript Object Notation (JSON). This call could allow an attacker to inject arbitrary elements or attributes into the JSON entity. Resolution: Investigation found that the JSON attributes are generated from the Java classes within ES, not derived from user input. No code changes were necessary. VES-9199 Problem: 5.14.0 Fortify: Privacy Violation - 3 issues. Resolution: Investigation found that the server hosting the application is configured and operated securely according to VA hosting facility policy and that the log files in question are protected from unauthorized read and/or write access. No code changes were necessary. VES-9202 Problem: 5.14.0 Fortify: Privacy Violation - 8 issues. Resolution: Investigation found that the classes reported (CleanUpPendingAdjudicationProcess.java and CCNServiceLogServiceImpl.java) are not using the CCNFileData as reported. No code changes were necessary. VES-9204 Problem: 5.14.0 Fortify: Race Condition: Singleton Member Field - 7 issues Resolution: Analysis found that the reported class is not a Singleton class so the rule does not apply to its members being shared between users. No code changes were necessary. VES-9273 Problem: 5.14.0 Fortify: Weak Extensible Markup Language (XML) Schema: Unbounded Occurrences - 50 issues. Resolution: Analysis found that ES inherits the schema and is not allowed to change it. In addition, any affected messages first pass through HealthConnect, which has validation rules that it follows before submitting to ES; therefore, the messages would fail in HealthConnect before reaching ES. VES-9379 Problem: Section 508: Focusable components in the content do not receive focus in an order that preserves meaning and operability. Resolution: Updated code so that Job Access With Speech (JAWS) reads the fields correctly. VES-9496 Problem: Enrollment and Eligibility (E&E) Service: Schema validation is failing for an Income Verification Match (IVM) request. Resolution: Fixed the XML tags so that the IVM retrieve request is successful. VES-9578 Problem: The "Send IVMUpdates" request in the E&E Service is throwing a Jakarta XML Binding (JAXB) unmarshalling exception error. Resolution: Fixed an incorrect annotation in the "SendIVMUpdatesRequest.java" code that was causing the error. VES-9581 Problem: E&E Service time stamp is different in new schema than in old schema. Resolution: Updated the format of the new schema to match the old service. VES-9715 Problem: E&E Service missing policy effective date tag in new schema. Resolution: Updated the format of the new schema to match the old service. VES-9932 Problem: Bidirectional Text (BIDI): Priority Group is not updated in ES on IVM conversion; Income Effective Date is removed in ES. Resolution: Added logic to parse incoming XML dates using alternate date formats. VES-9959 Problem: E&E Service: "SendIVMUpdates" tag name in new service response is not matching the old service. Resolution: Analysis found that IVM Bidirectional will work with either tag name as long as the "" and "" child elements match; no code changes needed. VES-9962 Problem: E&E Service: Extra tag is displaying in "retrieveIVMCandidates" response in the new service. Resolution: Analysis found that the extra tag will not break IVM Bidirectional; no code changes needed. VES-10175 Problem: Military service changes are being sent to VA Profile when the record is not actually changed; this causes unnecessary messaging and creation of duplicate work items in Cerner Millennium. Resolution: Modified logic to compare only the military service eligibility object for changes and not the entire collection. 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.14 Release Notes ES_5_14_RN.PDF ES 5.14 User Guide ES_5_14_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 : SEP 14, 2020 Completed By: Date Completed: NOV 23, 2020 Released By : Date Released : NOV 23, 2020 ============================================================================= Packman Mail Message: ===================== No routines included