21CFR Part 11 compliance¶
The 21CFR Part 11 compliance is supported, starting with visionCATS 2.0. It includes many administration and security features described in this section.
Note
This section does not describe the 21CFR Part 11 itself nor its implementation. It provides only a user-oriented view of its impacts in visionCATS.
Understanding the logging features¶
visionCATS contains many logging features, but the logging features related to the 21CFR Part 11 compliance consist of 2 separate loggers:
The System Logger, available at the application-wide level.
The HPTLC Logger, available in Method, Analysis and Comparison files.
All the important actions made in the visionCATS software are logged in the System Logger, whereas modifications made directly to an HPTLC item are logged in its own HPTLC Logger. However, there are overlapping actions, like some actions made in the Explorer view. For example, creating a new method inserts a log entry in the System Logger because there is a modification to the Explorer view, and a log entry in the HPTLC Logger of the newly created method to detail all its characteristics.
System logger¶
The System Logger logs automatically the important actions made by the users of the visionCATS software. It therefore builds a global history of the activity of its users. Each important action results in a new line in the System Logger, which contains essentially the timestamp of the action, the user and the message. The messages are also categorized in a 2-levels hierarchy to facilitate the future searches.
To access the System Logger, go to . This displays all the messages of the last 24 hours.
A full tabular view is available by clicking the Show full view button. This view provides the following features:
Filtering by
client (combo box): the machine name when the action occurred in the visionCATS application, or ‘visionCATS Server’
user (combo box): the user login when User Management is activated (‘visionCATSuser’ is the default user otherwise)
category and action (checkboxes and combo boxes)
date (date filter section) : the table shows by default the entries of the last week, but, by expanding the date range, all the entries since the installation of the system are accessible
text (text box) : textual search through the messages
Sorting, by clicking on the column headers (the table is by default sorted by date)
Pagination, by using the paginator on top of the table
Export (XPS export of the items, taking account of the current filter)
Client and User may not always refer to human users. The visionCATS software itself can record messages in the system logger when an important operation occurs without any user interaction. For example:
When migrating an HPTLC item during the installation of a new visionCATS version, the visionCATS installer insert system logger messages indicating which files it has created.
When a scheduled backup fails, the visionCATS server writes the issue in the system logger.
When a visionCATS application crashes, the visionCATS server closes the connection with the client after some time and logs the operation in the system logger.
HPTLC Logger¶
The HPTLC Logger (for methods, analysis and comparisons) logs all the modifications made to each HPTLC item in a tree. Each log item corresponds to an action (for example: the creation of the item, the execution of a step or the ‘save’ action after having modified some parameters) associated with a timestamp and the user who has issued the modification. When the value of a parameter is modified, the tree shows the old and the new value. More complex modifications, like lists or table modifications, are handled case by case but, at least, the log entry will always indicate that there was a change and display the new values. Globally, the structure of the tree follows the tab structure of the HPTLC item. For example, in case of an analysis, modifications are grouped by their location (Steps/Chromatography, Data, Spectrum, SST, Evaluation) and inside each evaluation, modifications are further grouped by tab (Definition, Integration, etc.).
In case of comparison files, the functionality is similar. The structure of a report entry follow the image/profile/spectrum/report structure.
To access the HPTLC Logger of an HPTLC item, open the HPTLC item (typically via the Explorer view) and then open the Log tab. This tab shows the history of all modifications made to the item. The following features are provided:
Navigate in the tree by expanding/collapsing elements and/or by using the helper buttons
Invert the chronological ordering of the log entries
Filter by date, user, area of modification
XPS Export
Data deletion¶
Note
This feature is only available on visionCATS installations where the 21 CFR Part 11 Compliance option is active.
By default, deleting an HPTLC item or a folder causes all its data to be lost. visionCATS administrators can modify this behavior by going to and checking/unchecking the corresponding options in the Options related to deletion of methods, analysis, comparisons and projects section:
The possible selection options are described in the following table:
Desired effect |
Selection |
|---|---|
|
|
|
|
|
|
|
|
Some specific rules apply when deleted items are marked as obsolete:
Deleting a folder is not allowed anymore, because folders can’t be obsolete in visionCATS.
It’s possible to restore the displayed obsolete items by using the corresponding command.
Motivated change¶
Note
This feature is only available on visionCATS installations having the 21 CFR Part 11 Compliance option.
For methods and analyses, it’s possible to force users to give a reason on each save by checking the Force users to enter a reason to each change on HPTLC items option in .
When this option is checked, a save on a method or on an analysis (with the exception of saves of changes consisting exclusively in automatically computed data) always shows the Motivated changes request window, and the motivation text entered by the user is saved in the HPTLC Logger.
E-Signature¶
Note
This feature is only available on visionCATS installations having the 21 CFR Part 11 Compliance option.
The visionCATS software provides a custom E-Signature solution for methods and analyses files. For comparison files, the E-Signature is done for each sample track, following otherwise the same rules. This solution requires the User Management to be activated and the E-Signature feature to be configured in the window, sections E-Signature levels and E-Signature user rights.
On a given file, an E-Signature starts at level 1 (called here Submitter). For each level, each user can/can’t sign files based on the items checked in the E-Signature user rights section table. A file already signed at level “n” can only be signed at level “n+1” if the level “n+1” has been defined. A user can’t sign the same HPTLC item on more than one different signing levels. Any modification to a file containing an E-Signature removes its E-Signature.
To sign a file, use the E-Sign… entry:
The E-Sign window always asks for credentials, and an optional comment. This information, associated with the current timestamp, constitutes the E-Signature itself.
After having signed a file, any save operation in it will result in a warning, indicating that the save will delete the E-Signature. E-Signature related information is shown directly in the explorer item row itself, next to the tabs displayed inside the HPTLC item when opening it, and a complete view of the whole signature is available in the Preview area:
Some special rules apply to signed elements:
When the E-Signature levels or names change, existing E-Signatures are kept as-is, but it’s not possible to further sign them.
When a file is imported from a foreign system, its E-Signature is kept as-is, but it’s not possible to further sign it.
Data integrity¶
As visionCATS saves data in a specific folder on the server, data integrity should be assured from the Windows rights.
As data are stored only on the server machine, it is recommend to install visionCATS server on a dedicated machine, on which only the IT Administration has access.
Otherwise (like for standalone installation), the data in the image folder should be protected with specific user rights. For more information, see How to setup Windows user rights for data integrity.
Note
As the database files are stored in the respective installation folder, any modification of it by a standard user is already blocked by Windows.