============================================================================= Run Date: APR 16, 2021 Designation: JLV*2.9*5 Package : JLV - JOINT LEGACY VIEWER Priority: Mandatory Version : 2.9 SEQ #5 Status: Released Compliance Date: APR 30, 2021 ============================================================================= Subject: JLV 2.9.2.1 Category: - Informational - Enhancement (Mandatory) Description: ============ ***************************** PLEASE NOTE ******************************* * * * Version 2.9.2.1 of the Joint Longitudinal Viewer (JLV) was promoted * * to the production server at 8 pm EST on 04/15/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.2.1 OEHRM Production Release includes enhancements to functionality as follows: JP-3261 - JLV 2.9.2.1 (EHRM/Cerner) Release Readiness Checklist JP-203 - Radiology Reports: Cerner Technical Update for Accessing Radiology Images JP-1347 - Documents: Cerner Technical Update for Accessing Radiology Images JP-2565 - Add Cerner API for Nutrition Orders JP-2885 - Cerner Blood Bank Report JP-3272 - NFR: Cerner Images Without Reports JP-3273 - NFR: Cerner Cardiology JP-2310 - Cerner FHIR API Demographics: Add SIGI to FEHR Tab JLV 2.9.1.2 OEHRM Production Release includes bug fixes as follows: JP-3230 - (Production) Cerner Legacy Prescriptions with incorrect fill date JP-3267 - (Production) Cerner FHIR API for Appointments is not working JP-3009 - (UAT) FHIR Lab Results- Blood Transfusion data displays as invalid individual result items JP-3237 - (Production)JLV erroneously displays a Last Fill Date in the Outpatient Medications widget for Cerner Millennium Documented medications with no fill occurred The requirements planned for the JLV 2.9.2.1 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_5_POM.PDF JLV Production Operations Manual: PDF format JLV_2_9_5_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.a spx Routine Information: ==================== No routines included. ============================================================================= User Information: Entered By : Date Entered : APR 13, 2021 Completed By: Date Completed: APR 16, 2021 Released By : Date Released : APR 16, 2021 ============================================================================= Packman Mail Message: ===================== No routines included