December 2020, SP8

  • dbLabCal exports results into csv, xml and SEND formatted files 
  • dbLabCal uses also barcodes as sample ID during data import and result export
  • dbLabCal imports data created with Gyrolab® instrument
  • dbLabCal imports data created with Agilent® ChemStation
  • various user interface improvements

February 2016, SP8

  • New function: dbLabCal imports data created with MSD® instruments with DISCOVERY WORKBENCH® Software
  • ICP-MS import improved
    dbLabCal can import either the intensity data or the net intensity data from results created with ICP-MS instruments controlled by the ELAN II (PerkinElmer®) Software
  • ELISA import and calculations improved
  • Windows 8.x  and Windows 10 compatibility
  • user interface improvements

June 2011, SP7

  • Analyst® data import improved
    dbLabCal expect the ASCII import file created with Analyst (SCIEX®) to be in the same folder with the respective Analyst’s rdb-file having exactly the same file name (e.g.: batch001.rdb – batch001.lca, batch002.rdb – batch002.lca etc.)  dbLabCal will lock the Analyst’s rdb file after successful import in that no data can be changed in Analyst after the data were once imported.
    dbLabCal imports automatically also chromatogram flags, ISR tag as well as all comments and annotations from Analyst’s result table
  • New function: Chromera import
    dbLabCal imports data created with ICP-MS instruments controlled by the Chromera (PerkinElmer®) Software
  • new batch status implemented “batch locked”
    Principal Investigator (PI) can lock all batch data, acceptance results, chromatogram flags as well as all project Settings
  • Project load dialog now with full text search
    allows user to find a project by any text in project codes, comment, analyte or matrix name
  • Force QC check
    dbLabCal’s results export is allowed only after the data QC check was finished in dbLabCal
  • System Audit Trail tracking database changes (user, permissions, DB options) added
  • Automatic MS Word export improved
  • Automatic data export according Roche’s “non barcoded” format added
  • Additional options in Option Statistics Dialog
    %accuracy calculation instead of %bias or %dev also possible
  • ISR usage in standard re-assays not allowed by default
    In case a sample had to be re-assayed because of ISR and also because of “standard re-assay reason” like bad chromatography etc., it is now by default not possible to choose final/reported value using the ISR
  • New function: Full 4 re-assay reporting
    It is possible to report any value and any “mean value combination” also having 4 re-assays if chosen in the “max.reassays drop down box in the “New Project” / “Edit Project” dialog. The limit so far was 3 reassays.

October 2010, SP6

  • New function: Data import from SearchLight®
  • New function: Direct data import from Empower2 (Waters®)
  • Immunoassay projects management improved
    Working range can be defined in addition to the calibration range as this is often required in Immunoassay projects
    New flag # is automatically set for results with CV outside the acceptance limit for double assays
  • New function: QC and QA function
  • QC and QA activities are documented in a special QC dialog and logged in dbLabCal’s audit trail

May 2008, SP5

  • New function: Data import from Magellan, Access2 and FACS instruments (Immunoassay)
  • New function: Data import from ISE (ion-selective electrode) controlled by MultiLab Pilot software
  • New function: ICP-MS instruments controlled by ELAN II software (PerkinElmer®) data import
  • New function: Electronic archive support
  • New function: Incurred Samples Reporting (ISR)
  • New function: Planning and automatic results reporting of long term stability experiments

November 2006, SP4

  • New rules for choosing final results from reassays samples added
    There are two new rules for choosing reassays (in addition to dbLabCal standard and the “Lang&Bolton” rule) – report first accepted result – report result according “Roche” rule
  • New function: SoftMax Pro data Import
  • Audit Trail view improved
    To improve the readability Audit trail view can be reduced after double click in Audit Trail view on some entry in the Action column just to the chosen action type entries. Repeated double click restores the Standard Audit trail view
  • Batch List View Filter improved
    A filter is available which allows to show and hide the sample types (CAL, QCS, VAL, SUB, SSS and DIV) directly in the batch list view

December 2005 SP3

  • New function: compliance to CFR 21 Part 11, Electronic Signatures
    dbLabCal V3 fulfills CFR21 Part 11 requirements. That means: – User has always to login – dbLabCal locks user automatically due to inactivity during certain period of time – Password has to fulfill security requirements and be changed periodically – Electronic signature required after specific actions
  • Project settings management improved
    It is possible to copy all settings (all data in sub-menu setting) from existing project into current project in the Project-New… and Project -Edit… dialogs
  • Acceptance criteria improved
    Acceptance criteria extended. Further, „IS check“ option was included into Acceptance criteria dialog. dbLabCal sets flag S automatically for all unknown samples, if their IS area (or height) is outside the set acceptance criterion
  • Final result reporting improved
    While setting the final results, the current user grants are considered. It means for example than an “Analyst” cannot overwrite a „Principal Investigator’s“ choice. User name of the user who set the final result is displayed in tool tip