We're delighted to present the latest updates and enhancements to MBioLIMS. This page describes the new features and changes we've made to give you an even better experience. Find out what's in store for you in this version and how it can benefit your use.
General
-
Additionnal information fields have been migrated to custom fields for all entities where applicable. As a result, existing imports that relied on additional information fields may be impacted.
-
The Print option in the navigation bar has been deprecated and is no longer available.
Patient
-
Administrators can now anonymize one or multiple patients from a new dedicated page. Individual fields can be cleared selectively, and all related events are deleted to ensure full compliance with GDPR data erasure requirements. Access is restricted to users with the appropriate administrative role.
-
When creating a new patient, the Hospital Patient ID (IPP in French) lookup is now triggered only when the Enter key is pressed. This prevents automatic searches on each keystroke and improves performance during HL7/Epic patient queries.
Visit
-
Visits can now be recorded for deceased patients or patients who have exited a study without being rejected, provided the visit date is prior the date of death or study exit.
-
Editing visits and samples is now allowed regardless of patient status, making it easier to correct or complete historical data.
Non-Compliance
-
When creating a non-compliance, you can now choose whether it should propagate to related entities. This allows you to block (or not) visits, samples, tubes, and derived tubes according to your needs.
-
You can now add a non-compliance to a patient inclusion in a specific study. This blocks the use of the patient’s tubes for that study while maintaining standard propagation to visits, samples, tubes, and derived tubes.
-
Non-compliances added at the patient level can also propagate to all of the patient’s inclusions.
-
A default propagation behavior can now be defined when configuring a non-compliance reason. Existing reasons have been migrated with propagation enabled. This setting is included configuration import/export.
-
The non-compliance creation section has been removed from the creation forms for Reception, Visit, and Transformation.
Non-compliances can still be created from the entity details page once the entity has been created.
User Account
-
Administrators with the new “System – Consult application logs” role can now access application logs.
Import / Export
-
Non-compliance propagation is now optional in legacy data imports. A new column in the import file allows you to specify whether each non-compliance should be propagated.
-
A new column in the Non-compliance reason import allows to set up the propagation default value.
-
When importing institutions, if multiple institution types need to be created, they must now be defined in a single row.
Resolved issues
-
Quick search loading performance has been improved
-
The user login is now included in application stdout logs.
-
All container types are now displayed again in the storage tree view, even when more than 20 container types exist.
-
Fixed an issue preventing the entire list of elements from the “Transferred elements” panel from being added to the working list.
-
Fixed an issue where two sample sheets appeared in legacy data imports under certain configuration.
-
Fixed an issue where non-compliances were not correctly propagated to tubes when a visit was associated with a reception
-
Non-compliances applied to a reception now also propagate to the tubes from the linked visit, as expected.
-
Fixed an issue where some tube statuses were not visible in statistics.
-
Fixed an issue where, in some cases, legacy imported shippings could not be deleted.
-
Fixed an issue where batch import completion notifications were not sent. Users now receive a notification when an import finishes, indicating success, rejection, or error.
-
Shipping reasons can now be queried from the reporting view RPR_EXPEDITION_VIEW.
-
Fixed an issue where custom fields of type checkbox were checked by default in edit mode.
-
Fixed an issue where some assay results were returned in advanced query results when they should not have been.