December 2016/January 2017 - SimCapture On-Premise Version 5.8.1
The complete history of the SimCapture On-Premise 5.8.1 release
Table of Contents
We are happy to bring you these new releases and always want to hear what you have to say! Any feedback is welcome, and we encourage you to contact our support team with any of your comments or questions. They can be reached at SimCaptureSupport@laerdal.com or 877-LAERDAL.
This article contains the complete history of the SimCapture On-Premise 5.8.1 release including any LLEAP releases, hardware and security updates.
Release version 5.8.1
Laerdal Medical is happy to announce the release of SimCapture version 5.8.1. For this new version, we focused on driving overall performance improvements for the system.
For more information about upgrading your system to SimCapture 5.8.1, please contact our support team via email at SimCaptureSupport@laerdal.com or call 877-LAERDAL. Previous release notes, documentation, and further updates can be found on the Laerdal Medical Customer Solution Center.
New features
Improve centralization performance
More innovative system logic to better regulate traffic between SimCapture devices and the central server.
Feature highlights
- The system will monitor SimCapture devices' activity and intelligently regulate traffic to help prioritize centralization for devices in active use.
- This update requires a configuration change, so please contact the SimCapture support team for assistance.
Bug fixes and improvements
- We have resolved an issue with creating a scheduled event with automatic recording, which allowed selecting a Course without specifying a Scenario.
- Fixed a problem where the ordering of IP camera streams on the Exam System's preview screen did not match how the camera streams appeared in the monitor interface. (CCM Clients Only)
- As a follow-up from a bug fix from the last release around METI simulator integration, we also resolved an issue where the upload of files works, but the data trends tab was not showing. Everything now shows up in the event log.