============================================================================= Run Date: FEB 18, 2021 Designation: JLV*2.9*4 Package : JLV - JOINT LEGACY VIEWER Priority: Mandatory Version : 2.9 SEQ #4 Status: Released Compliance Date: MAR 04, 2021 ============================================================================= Subject: JLV 2.9.2 Category: - Informational Description: ============ ***************************** PLEASE NOTE ******************************* * * * Version 2.9.2 of the Joint Legacy Viewer (JLV) was promoted * * to the production server at 10 pm EST on 02/17/21. * * * * * * NOTE: This patch was loaded on the National JLV server. There is * * nothing that local sites can or need to do besides communicate * * changes to users. * * * ************************************************************************* JLV version 2.9.2 includes enhancements to functionality as follows: - CAPRI/Claims SSOi: Ability to utilize IAM single sign-on to authenticate against the Claims system - Demographics: Update Primary Care Provider Logic - Rename Master Veteran Index to Master Person Index - Cerner FHIR API (Patient Address) - Cerner Documents API (JLV FEHR/MHS Genesis, JLV Documents) - Keep Patient Name Visible When Window Maximized - JLV Claims URL Redirect Landing Page - Widget Name Change (VistA Only - Clinical Reminders, Health Summaries and Reports) JLV version 2.9.2 also includes bug fixes as follows: - Modify VA SSOi interface to login site value passed - Report Builder (Demographics Update PCP Logic Display, Demographic FEHR sites SC Percent and SSN Label, Display Address Use Field Above Primary Address) - Widget Tray - Clinical Reminders doesn't change with new label Participating Test Sites: The requirements planned for the JLV 2.9.2 Iterations 1-4 were verified and validated during the Development Independent Testing (DIT) phase of testing. All requirements mapped to the test scripts. The scripts are designed to be end-to-end functional tests of the system to evaluate all the technical requirements including the testing of external interfaces where appropriate. The DIT cycle consisted of smoke testing and the formal DIT. Before starting the DIT cycle, a JLV Web application baseline or release tag is installed on the system. Tests are then run against this software baseline/release tag. Any issues found and potential resolutions are assessed for possible inclusion in the software baseline. During DIT, the test team validated the requirements provided in the JIRA JP Project requirements collection using the test scripts and the test Cases in TestRail. Any issue encountered is recorded as a defect in the JIRA JP Project. Documentation Instructions: ========================== Sites may retrieve the documentation directly using this website: https://download.vista.domain.ext then select the SOFTWARE directory File Name Contents --------- -------- JLV_2_9_2_USERGUIDE.PDF JLV User Guide: PDF format JLV_2_9_2_POM.PDF JLV Production Operations Manual: PDF format JLV_2_9_2_DIBR.PDF JLV Deployment/Install/Backout/Rollback Guide The JLV user guide, resources and training materials are also posted and updated on the JLV website: http://vaww.oed.portal.domain.ext/pm/iehr/vista_evolution/JLV/SitePages/ Home.aspx Routine Information: ==================== No routines included. ============================================================================= User Information: Entered By : Date Entered : FEB 09, 2021 Completed By: Date Completed: FEB 18, 2021 Released By : Date Released : FEB 18, 2021 ============================================================================= Packman Mail Message: ===================== No routines included