12.01.2014 Views

Software Manual Freedom EVOware Standard 2.3 Freedom ...

Software Manual Freedom EVOware Standard 2.3 Freedom ...

Software Manual Freedom EVOware Standard 2.3 Freedom ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

B - Appendix B - FDA 21 CFR Part 11 Compliance<br />

Security Features in the <strong>Software</strong> Which Assist 21 CFR Part 11 Compliance<br />

Fig. B-1<br />

Password prompt with the Electronic Signatures feature active<br />

After confirming the entries by clicking OK, an electronic signature is executed<br />

and an entry is made in <strong>Freedom</strong> <strong>EVOware</strong>’s trace file.<br />

The Data Explorer can be used to view the user comment for each of these files<br />

(see A.9.1 “Data Explorer Tool”, A-35). Only the most recent comment is saved<br />

in the file. Earlier comments are stored with previous versions of these files, which<br />

are automatically backed up to the \AuditTrail\Configuration<br />

directory (see A.5 “<strong>Freedom</strong> <strong>EVOware</strong> Directory Structure and Files”, A-25).<br />

The plain text header of each file can also be viewed independently of <strong>Freedom</strong><br />

<strong>EVOware</strong> using a suitable editor. The following information is stored in the header:<br />

• CRC checksum<br />

• Date and time of creation or modification<br />

• User name<br />

• User-specified reason for the change (if the Electronic Signatures feature is<br />

enabled in the <strong>Freedom</strong> <strong>EVOware</strong> Configuration Tool)<br />

• User’s full name<br />

A user comment is required by 21 CFR Part 58 (GLP) but not by 21 CFR Part 11,<br />

although some customers want to record this type of information anyway.<br />

If one of the above changes has been made automatically by <strong>Freedom</strong> <strong>EVOware</strong>,<br />

a comment is inserted which starts with “<strong>EVOware</strong>:”<br />

B.5.6 Trace File (Audit Trail)<br />

The trace file contains information on configuration, data and log files which have<br />

been created, edited or saved. The default location for the trace file is<br />

\AuditTrail\Log.<br />

Each time a configuration, data or log file is created or modified, a CRC checksum<br />

is stored in the file and an entry is made in the trace file.<br />

Each entry in the trace file specifies the date and time, the name of the currently<br />

logged in user and the file name. Log files are created by <strong>Freedom</strong> <strong>EVOware</strong><br />

automatically and a user name is not included in the trace file entry in this case.<br />

The trace file can be viewed with a plain text editor.<br />

Each time a configuration or data file is modified and saved, the previous version<br />

is archived in the \AuditTrail\Configuration sub-directory. The date<br />

and time is appended to the original filename. The archive copy includes the userspecified<br />

reason for the change if “Electronic Signatures” is enabled in the<br />

<strong>Freedom</strong> <strong>EVOware</strong> Configuration Tool (see B.5.5 “Electronic Signatures”, B-9).<br />

B - 10 <strong>Freedom</strong> <strong>EVOware</strong> <strong>Software</strong> <strong>Manual</strong>, 393172, en, V<strong>2.3</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!