back to manual overview

Automatic Labordatenbank validations

With this tool, you have the capability to create and execute validations independently, ensuring the proper functionality of the laboratory database automatically.

Purpose of a Validation

The purpose of validation is to create automated checks that ensure the accuracy of the laboratory database's functionality. This includes verifying the correctness of parameter formulas or confirming the proper functioning of the database following updates made by us.

You can find the validation under: Navigation Bar Settings Validation

① Under Create Test, you can create validations in the following 6 areas:
› Parameter Formulas
› Reports
› Specification
› Access rights
› SQL report
› Pricelist suggestions

② Under Start Validation , you execute all tests. The results are displayed under Validation reports with a success rate.

③ Under Category, you can view the respective tests that have been assigned to a specific category.

④ You can also generate the report as a PDF by clicking on the Report button.

⑤ In the Validation Reports section, you can track when and by whom the last validation was performed and the extent to which it was successful.

⑥ In the Test Coverage section, you have the opportunity to check the extent to which the validation covers your system. Additionally, you can view all functions that are not covered by a validation.

⑦ Here, you'll find all validation tests you've created or selected under the Category. On the right side, you can also see when the last validation test was conducted and whether it was successful. In case of failure, you can investigate where the validation failed under Show Details. Additionally, you can review validation examples in all possible categories at the bottom.


Validation Example for Parameter Formulas


You can check the result of a sample, such as the pH value of a sample: To do this, you need to select a sample and set its reference value. If a sample is outside the set value, it will be marked as Failed during validation.



Validation Example for Reports


When creating a report, a unique HASH is generated. If there are changes to the design or tables, a new HASH is generated. Validation checks if the HASH values match. If they do not, the validation marks these reports as failed.



Validation Example for Limit Tables


Based on the pH value, it can be determined whether the sample should be within the defined range, below pH 7, or above pH 7. In this case, the sample is marked as "passed" if it is within the range, or as "broken" if it is outside the range.



Validation Example for Access Rights


Regarding access rights, you have the option to check if certain employees have the required access rights. If someone has more access rights or is missing some, they can be checked through validation.



Validation Example for Evaluation


An evaluation example could be checking if employees have a password that is older than 6 months. If the evaluation finds that some employees are using older passwords, these employees will be marked as failed during validation.



Validation Example for Billing Proposals


In the billing proposals, you can check, for example, whether price changes have occurred in an order, whether discounts are applied correctly, and whether changes in new investigation packages are correctly taken into account.

Last change: 10.01.2025

Allgemeines

Einführungsphase

Mitarbeiter

Aufträge

Proben

Probenvorlage

Berichte

Berichtstabellen Editor

Kunden

Kundenzone (optional)

Anlagen

Angebote

Rechnungen

Parameter

Rechnen mit Parametern

Schnittstellen

Webservice

Transformationscode

Prüfpläne / Grenzwerte / Spezifikationen

Dokumentenlenkung

Prüfmittel

Material

Mitarbeiterschulungen

8D-Report

Sonstiges

PDF-Vorlagen

Fragen und Antworten

Lieferantenbewertung

Dateiverwaltung

Auswertungen

Prozesse