=============================================================================
Run Date: SEP 24, 2021                     Designation: JLV*2.9*13
Package : JLV - JOINT LEGACY VIEWER           Priority: Mandatory
Version : 2.9        SEQ #13                    Status: Released
                  Compliance Date: OCT 08, 2021
=============================================================================


Subject: JLV 2.9.5.1.0 EHRM Svc 2.9.5

Category: 
  - Informational

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

 ***************************** PLEASE NOTE *******************************
 *                                                                       *
 * Version 2.9.5.1 of the Joint Longitudinal Viewer (JLV) was promoted   *
 * to the production server at 11pm EST on 09/23/2021.                   *
 *                                                                       *
 *                                                                       *
 * 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 2.9.5.1.0 Patch updates the EHRMService module received from Office 
 of Electronic Health Records Modernization (OEHRM). The EHRMService 
 upgrades the Medications Fast Healthcare Interoperability Resources 
 (FHIR) Application Programming Interfaces
 (APIs), filters out duplicative data resulted from bulk VistA data 
 migration, enables error logging for EHRMService, and displays improved 
 simplified site/location names for all FHIR API data.
  
 The following documentation change records are included in this release:
  
 Issue key | Summary
 -- | --
 JP-2942 |       Cerner FHIR Filter Migrated Data
 JP-3650 |       (Production) FEHR (Cerner) Expired Documented medications 
 are included in the FHIR API and are not distinguishable from Active 
 Documented medications
 JP-5718 |       EHRMService Logging
 JP-6305 |       EHRMService 2.9.5.1.0 Release Readiness Checklist
 JP-6367 |       Friendly Name for Site from Millennium for all FHIR API 
 Data
 JP-6369 |       NFR: Medications FHIR API upgrade to R4 
 JP-6389 |       (UAT) FEHR active documented meds missing
 JP-6397 |       (UAT) FEHR active meds not captured with â ~Copy active 
 rx button
 JP-6405 |       (UAT) FEHR site name is No Facility Access
 JP-6410 |       (UAT) Duplicate Orders with Different Order Numbers  
 JP-6411 |       (UAT) Incorrect details for Pharmacy charge order type in 
 the Medications-Outpatient widget   
 JP-6412 |       (UAT) Expired migrated Legacy Prescriptions do not 
 display with R4
 JP-6452 |       (UAT )FEHR Outpt meds display false dispense dates
 JP-6453 |       (UAT ) FEHR Outpt meds do not display Last Fill Dates
 JP-6470 |       (UAT ) Issue with Order Type mapping - Re-map Order Type 
 of Prescription/Discharge
 JP-6471 |       (UAT ) Issue with Order Type mapping - Re-map the Order 
 Type of In-office order (outpatient)
 JP-6472 |       (UAT ) Append (Clinic medication) to medications 
 displayed in the Medications 
 JP-6476 |       (SQA) Medications OutPt - "Order Start Date" text 
 displays when there is no date in the Last Fill column for FEHR source
 JP-6477 |       (SQA) Medications Outpt. - Date is missing in the Last 
 Fill column for FEHR source
 JP-6478 |       (SQA) Medications OutPt. - Missing appended text "Order 
 Start Date" to clipboard upon using Copy Active Rx button
 JP-6518 | HPS AC Concurrence on Info PD (FORUM)
 JP-6307 | Version Description Document (VDD)
 JLV 2.9.5.1 Deployment Checklist
  
 Participating Test Sites:
  
 The requirements planned for the JLV 2.9.5.1.0  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:
  
 No formal documentation included in release.
  
 ==========================

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

=============================================================================
User Information:
Entered By  :                               Date Entered  : SEP 21, 2021
Completed By:                               Date Completed: SEP 24, 2021
Released By :                               Date Released : SEP 24, 2021
=============================================================================


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

No routines included