The addition of FastFinder Workflow marks a milestone in the continued evolution of the FastFinder platform. FastFinder Workflow allows labs to track samples, plates and assays throughout the lab, providing a full audit trail and chain of custody from when a sample hits the first instrument in the workflow, to the point where the results enter the LIMS system. Orchestrating the sample flow, FastFinder Workflow is an integral part of the FastFinder platform and integrates tightly with FastFinder Analysis to seamlessly support analysis and interpretation support as part of the broader lab operations. This release also marks user interface and performance improvements for FastFinder Analysis 4.1. Lastly, the release also marks updates to the Lab Management component of FastFinder, providing centralized assay, instrument and user management.
The addition of Workflow 1.0 to the FastFinder platform implements key capabilities to track samples throughout the lab trajectory (cfr. Workflow 1.0 & Lab management 1.1). This capability is also available in the Samples module in Lab Management 1.1
With efficiency requirements for routine labs in mind, the team incorporated feedback from end users to improve UI/UX aspects of Analysis 4.1.
For the specific release notes for Lab management 1.1 see (link) and for Workflow 1.0 see (link)
For a general description on supported systems, security measures, and traceability, please see the IFU.
Analysis 4.1.2 (Dec 1, 2020)
Analysis 4.1.1 (Nov 26, 2020)
Specific usability improvements include addition of edit capability in the Summary view, improvements to plate performance, and improved CFX instrument support.
The following issues have been fixed in the Analysis 4.1 release:
Re-analyzing an analysis with an inactivated Assay Plugin resulted in a Failed analysis.
Cobas z480 support.
Opening an analysis returned an error ("Cannot read property 'x' of undefined") due to failed loading of fluorescence values.
Deselecting wells in plate view did not deselect the corresponding curves.
When changing a result, the audit trail mentioned Positive and Negative instead of Detected and Not detected.
Article is closed for comments.