MBioLIMS Sugiton 25

17 Jan 2025

We’re delighted to present MBioLIMS Sugiton! The latest version is now available, bringing you powerful new tools to enhance your sample management process.

We are proud to be based in Provence, a beautiful region in southeastern France known for its stunning landscapes and rich heritage. To reflect our connection to this unique area, each major release will now be named after an iconic location in Provence. Our headquarters are located in Marseille, and MBioLIMS 25 has been named “Sugiton”, after the breathtaking Calanque de Sugiton, a scenic Mediterranean cove near our offices. (For those interested, you can learn more about it here: Calanque de Sugiton on Wikipedia.)

As part of this release, we are introducing a new versioning scheme to enable easier and more frequent improvements. Going forward, MBioLIMS versions will follow the format: Major.Minor.Hotfix, allowing us to deliver enhancements more efficiently.

General

• Simple searches now offer more flexibility with new display modes: gallery and calendar. These views can be customized using the existing configuration button. Additionally, you can now easily show or hide the filters you want to use for each search.

• We have refined the role management for accessing administration pages. This new structure allows you to assign only the necessary permissions to each user profile. After updating to MBioLIMS 25, we recommend reviewing user profiles to ensure everyone has the required access.

• Duplicate search pages, previously accessible but redundant with administration pages, have been removed. For access to the relevant administration pages, consult your administrator.

• The “Current study” feature has been removed.

• The “Operator” field has been removed from documents and protocols.

Visit

• We have streamlined the management of visits and sample collections by merging the “Visit” and “Sample Collection” entities. This unification allows for a smoother process when recording samples. A new “realization date” field is now available at the sample level, enabling you to specify different dates for each sample within the same visit, improving tracking and flexibility.

• It is now possible to not only confirm but also cancel a scheduled visit. If canceled, the visit and its associated tubes will automatically move to the “Canceled” status.

• Patient IDs are now displayed in the visit search, providing quick access to patient records.

• The Hospital internal ID is now displayed on the visit page.

• The AFN field, formerly a standard field used by HL7 in the context of visits, has been moved to the corresponding module and will only be visible when the HL7 module is active.

Collection

• We have improved collection handling on sample containers:

  • when creating a visit, it is now possible to enter one or more values individually for each tube

  • it is now possible to set default values in the administration of the visit type

  • it is also possible to edit a sample container’s collection directly from the tube or plate page.

Sample

• The new “realization date” field on samples is now editable. Updating this date will automatically adjust the realization date for any directly linked tubes (those not derived from aliquoting) to match, ensuring consistency across related records.

• The “Hospital patient ID” is now displayed on the tubes search page.

• We've removed the action buttons with arrow icons from the “Sample summary” panel on the tube page.

Patient

• We've moved the Patient inclusion search to a dedicated page, where it's possible to see all the standard and custom fields of patient inclusion.

• The “Hospital patient ID” field must now be unique. If multiple patients share the same “Hospital patient ID”, you must update this field with a unique value or clear it before saving any changes.

Kit

• We've moved the “Create kit shipping” menu to the “Shipping” tab.

Transformation

• The default values for the “Pool”, “Take all” and “Sample containers with barcodes” fields of a transformation can now be set in the administration of each transformation type.

Shipping

• To align with other entities, the “Request Number” field in shipping requests is now called “ID.”

Reports

• The RPR_INSTITUTION_DEPARTMENT_VIEW, RPR_CSF_INSTITUTION_VIEW, RPR_CSF_DEPARTMENT_VIEW and RPR_CSF_CONTACT_VIEW views for accessing data on institutions, departments and their contacts are now available.

• Tube and sample realization dates are now available in RPR_TUBE_VIEW.

• The view RPR_CSF_SPECIMEN_COLLECTION_VIEW has been renamed RPR_CSF_VISIT_VIEW.

User Account

• Avatars can now be deleted.

Custom Field

• You no longer need to include “http://” in custom URL fields.

Import / Export

• Imports are now more efficient, especially for files with a large number of custom fields. If an entity appears on multiple rows (like visits with multiple tubes), its information (custom fields and non-required standard fields) can now be entered only on the first row. In addition, events on different entities are no longer recorded as part of legacy data imports.

• We have improved the time taken to export settings when the entity contains custom fields.

• It is now possible to include a reception in the sample legacy data import file (for studies without patients).

• We have improved the “Visit type - Expected samples” settings import by introducing the “Sample #” column. This new column allows you to differentiate between samples within the same visit type and to define different configurations, even for samples of the same type.

• Checks on the Import patient file from HL7 have been improved.

• In order to reduce our environmental footprint, we will no longer be sending automatic e-mail messages when a file import is complete. You will, however, continue to receive the in-app notification.

API - Webhook

• It is now possible to know the species entered in the taxonomy and the values of their custom fields by using the endpoints /api/species, /api/species/{id}, /api/species/{id}/custom_field_values and /api/species/{id}/custom_field_values/{idCF}.

• It is now possible to know the storage constraints applied to a container with the endpoint /api/containers/{id}/constraints.

• The /api/samples/{id} endpoint has been enhanced to return all information concerning the strain and study to which the sample belongs.

Resolved issues