Florence eBinders: General Electronic Log (eLog) Functionality UW User Guide

Florence eBinders^TM includes electronic logs (elogs) and this document describes some of the general functionality associated with them. It also includes information on why we do not use the log duplication functionality at our site.

Do not use log duplication functionality
Importing Rows
Log Up-versioning
Log Row Up-versioning

Do not use log duplication functionality

On 30MAR2026, Regulatory Staff and Study Coordinator roles in eBinders automatically updated to include a permission that allows for the duplication of logs. Due to risks associated with this functionality, it is not to be used, and our site will not provide support for its use. Below is a brief summary of the risks:

Limited audit trail - the first audit trail entry of the duplicated log is limited to displaying the location of the original log; it does not include actions or responsible personnel previously captured in the audit trail of the original log
Log Details copy over without notification to user - information like OnCore/IRB/Sponsor study numbers and Principal Investigator and Sponsor Names are study-specific and users are not warned that these details are to be updated with duplication
Log row entry data copies over, even if inaccurate for duplicate log - for example, if you duplicate the DOA log from one study for another, data like start dates copy over regardless of accuracy for new study
Log data correction updates take more time and effort than using the alternative method of importing rows or entering data on a newly created log using the appropriate template

Alternative functionality to save time when creating logs:

The Importing rows functionality allows you to save time by populating certain data into a log using a spreadsheet.
Example: If you create a lot of delegation of authority (DOA) logs, you can maintain a single spreadsheet with the list of study team members, roles, and duties. For each new study, you can easily update things like duties (to align with the legend) and start dates (copy and paste) in the spreadsheet before upload.
For more information refer to the Importing Rows section in of this KB page.

Importing Rows

For written instructions and a video on how to use Importing rows, refer to the Florence Support import rows in bulk article (sign-in required)
Note(s) about the spreadsheet:
- - Changing column headers will cause errors upon upload
  - Dates must be formatted as either DD/Mmm/YYYY (e.g., 01/Jan/2022) or DD-Mmm-YYYY (e.g., 01-Jan-2022)
  - Signature columns must be left blank
Note(s) about usage:
- Do not use the import feature to update rows, as the system does not recognize repeat entries and will make additional rows instead of editing existing entries.
- If you erroneously add an entry, you can strikethrough the row and provide a reason for doing so for the audit trail. It is not possible to DELETE a row. If you see the word DELETE in a warning pop-window prior to completing the deletion, this is referring to the deletion of the ENTIRE LOG.