=============================================================================
Run Date: JUN 03, 2021                     Designation: JLV*2.9*9
Package : JLV - JOINT LEGACY VIEWER           Priority: EMERGENCY
Version : 2.9         SEQ #9                    Status: Released
                  Compliance Date: JUN 07, 2021
=============================================================================


Subject: JLV 2.9.4.0.1 addresses defects to resolve the in1

Category: 
  - Informational

Description:
============

 JLV 2.9.4.0.1 hot patch resolves the inability to open certain file 
 formats (e.g., MHT, RTF, TIF) by either opening those new formats or 
 directing users to the browser's download options. This release also 
 corrects the site name and hover over message for radiology images 
 originating from Federal Electronic Health Record (FEHR) sites in the 
 Imaging and Radiology Reports widgets and updates error handling for 
 retrieval of the EHRM Blood Bank report.
  
 JLV 2.9.4.0.1 release includes the following change records:
  
 Issue key | Summary
 -- | --
 JP-3645 | Operational Request - Reminders Inclusion List Update
 JP-2755 | (Production) CommonWell Doc Types PDF/IHE 1.x Not Opening
 JP-3781 | Cerner Pull Request #189 - Add reader close to   
 EHRMBloodBankTransfusionNames
 JP-3791 | (UAT) FEHR (MHS G) Radiology Images display incorrect Site 
 Names and   Hover Over
 JP-4998 | (Production) JLV hangs or spinning upon clicking on the Patient 
 Name of the Detailed Demographics 
 JP-5001 | (Production) VistA and DoD Vital Signs missing in JLV for any 
 patient having Vitals data from the FEHR
  
 The requirements planned for the JLV 2.9.4.0.1 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.
  
 No Documentation Impacts for this release. 

Routine Information:
====================
No routines included.

=============================================================================
User Information:
Entered By  :                               Date Entered  : JUN 01, 2021
Completed By:                               Date Completed: JUN 03, 2021
Released By :                               Date Released : JUN 03, 2021
=============================================================================


Packman Mail Message:
=====================

No routines included