Skip to main content
v2026.11,986 entries · CC-BY 4.0

Florence eBinder: Clinical Research eISF Guide

Learn how clinical research teams use Florence eBinders for 21 CFR Part 11 electronic investigator site files, ePrinter routing, and remote monitoring.

Written and maintained by CASRAI Editorial Board

Published · Last updated

On this page

What it is used for in research

Florence eBinder (developed by Florence Healthcare as Florence eBinders) is a specialized cloud-based electronic Investigator Site File (eISF) and regulatory document management platform designed for clinical research sites, academic medical centers, and health systems. In clinical trials governed by Good Clinical Practice (ICH GCP E6(R2)) and FDA regulations (21 CFR Part 312 for investigational new drugs and 21 CFR Part 812 for investigational devices), research teams are legally required to maintain essential regulatory documents demonstrating trial compliance and data integrity, often referencing safety and regulatory datasets from openFDA for investigational product surveillance.

Historically, clinical trial sites maintained physical paper binders—often dozens of three-ring binders per protocol containing investigator brochures, Form FDA 1572 submissions, Institutional Review Board (IRB) approvals, delegation of authority (DOA) logs, and financial disclosures. Florence eBinders replaces these physical binders with a centralized, 21 CFR Part 11-compliant digital architecture. Within an academic medical center or clinical research organization, study personnel such as a Certified Clinical Research Coordinator (CCRC) or Certified Clinical Research Professional (CCRP) rely on the platform to execute several vital research operations:

  • Electronic Investigator Site File (eISF) Maintenance: Systematically files, versions, and indexes essential trial documents according to standardized folder taxonomies mapped to ICH GCP guidelines.
  • Part 11 Compliant Electronic Signatures: Executes legally binding digital signatures on protocol amendments, delegation logs, and safety acknowledgments using secure two-factor credentialing with an audit trail.
  • Remote Monitoring and Site Initiation: Provides external clinical research associates (CRAs), contract research organizations (CROs), and trial sponsors with secure, role-scoped remote access to study records, facilitating remote source data verification without requiring on-site physical visits.
  • Investigator Credential Distribution: Allows research sites to upload common staff credentials (e.g., curriculum vitae, medical licenses, and GCP training certificates) once to an investigator profile and push updates simultaneously across all associated study binders.
  • Integration with Research Infrastructure: Interfaces directly with Clinical Trial Management Systems (CTMS) like OnCore, electronic health records (EHR), and laboratory data infrastructure, complementing a broader Scientific Data Management System (SDMS) environment.
  • Audit and Inspection Readiness: Produces timestamped, unalterable audit trails and document logs required during an FDA inspection or a sponsor second-party audit.

How to install or access it

Florence eBinders is a Software-as-a-Service (SaaS) web application hosted in a secure cloud infrastructure. It requires no local server deployment by research staff, but site personnel must follow specific administrative and onboarding protocols to gain verified access:

  • Official Web Access Gateway: Authorized research teams log in directly through the vendor portal at https://www.florencehc.com/sign-in/ or their institution-specific subdomain.
  • Training Prerequisite (Florence Academy): Institutional policy at academic research centers (such as UC Davis Health and Medical College of Wisconsin) requires all end-users—including Principal Investigators, study coordinators, regulatory managers, and external monitors—to complete mandatory role-based training modules via the Florence Academy (https://academy.florencehc.com/register-and-login) before production accounts are provisioned.
  • Institutional Account Provisioning: Following training verification, study staff submit an access request through their institution’s research administration portal (such as ServiceNow or the local CTMS operations office). An automated activation invitation is dispatched from [email protected].
  • Account Activation and PIN Setup: Users activate their account using their official institutional email address, accept the electronic record and signature terms of use, and configure a dedicated Florence signing PIN used for dual-factor authentication during document execution.
  • Florence ePrinter Installation: To ingest digital records directly from electronic health records, CTMS platforms, or local desktop applications without saving unencrypted intermediary files, users download and install the official Florence ePrinter utility from the application’s user tools menu onto their institution-managed Windows or macOS workstation.

Step-by-step instructions

The following walkthrough details the standard workflow for setting up a new study regulatory binder, creating document placeholders, ingesting clinical trial records via the Florence ePrinter, and executing a 21 CFR Part 11-compliant electronic signature.

  1. Access the Study Binder and Configure Team Roles:
    • Log in to the Florence eBinders platform using your institutional credentials.
    • From the top navigation bar, click Study Binders and select the designated trial protocol.
    • Click the Team and Roles tab in the binder settings panel.
    • Click Assign Member, search for the research personnel by institutional email, assign their protocol role (e.g., Principal Investigator, Sub-Investigator, or Coordinator), and set their permission level to Edit and Sign or View Only. Click Save Changes.
  2. Apply the Standardized eISF Folder Taxonomy:
    • Navigate to the binder root view and select Binder Settings → Structure Templates.
    • Select the ICH GCP Section 8 Essential Documents Template, which automatically constructs regulatory directories for Protocol and Amendments, IRB Correspondence, Form FDA 1572 / Investigator Agreements, Financial Disclosures, and Staff Qualifications.
    • Click Apply Template to populate the folder hierarchy.
  3. Create Document Placeholders with Task Assignments:
    • Open the target folder (for example, 04_IRB_Approvals or 02_Protocol_Amendments).
    • In the upper-right folder toolbar, click Add Placeholder.
    • In the modal window, enter the Document Name (e.g., IRB Continuing Review Approval Notice 2026), select the document category, set the Due Date, and select the assigned coordinator from the dropdown list.
    • Click Create Placeholder. The placeholder appears in the folder view with a status badge of Pending Upload.
  4. Route Records Directly Using the Florence ePrinter:
    • Open the target document (such as an IRB approval memo or trial safety update) in your browser, CTMS, or PDF viewer.
    • Select File → Print (or press Ctrl+P / Cmd+P).
    • In the printer destination dropdown, select Florence ePrinter and click Print.
    • The Florence desktop routing window appears. Authenticate with your institutional credentials if prompted.
    • Select your target Study Binder, navigate into the destination folder, and select the corresponding Placeholder created in Step 3.
    • Click Upload to eBinder. The virtual driver converts and encrypts the document into an immutable PDF, fulfills the placeholder, and uploads it directly to the cloud repository without writing unencrypted temporary files to local storage.
  5. Initiate and Complete Electronic Signatures:
    • Navigate back to the uploaded document in the Florence web workspace and click Open Document.
    • Click the Signatures menu in the document header and select Request Signature.
    • Select the signing individual (e.g., Principal Investigator), specify the signature reason (such as Approval of Protocol Amendment or Review and Verification), drag the signature placement box to the designated signature line on the document, and click Send Request.
    • The Principal Investigator logs in, opens the pending signature notification, reviews the document text, and clicks Sign Document.
    • In the security verification modal, the signer enters their account password and their confidential Florence Signing PIN, then clicks Authorize Signature.

Output and how to read it

Executing workflows within Florence eBinders generates structured regulatory outputs, compliance audit trails, and status reports that study teams and monitors use to assess binder health:

  • Electronic Signature Manifest and Certificate of Completion: When a document is signed, Florence appends an immutable signature stamp to the document face and generates an attached Certificate of Completion. The certificate displays the signer’s full name, email address, role, exact timestamp recorded in UTC, IP address, cryptographic document hash (SHA-256), and the legal reason for signing per 21 CFR Part 11. Reading this output confirms that the digital record has not been altered or tampered with since execution.
  • Granular Audit Trail Logs: Every action performed on a binder item—including document creation, version replacement, placeholder fulfillment, permission modification, and viewing activity—is automatically logged in the system audit trail. Clicking Document Details → Audit History reveals an chronological log. Auditors review the Action, User ID, Timestamp, and Previous Value / New Value fields to verify continuous chain-of-custody.
  • Staff Credential and License Expiration Dashboard: The Compliance Dashboard summarizes staff qualification status across all active studies. It uses standardized status indicators:
    • Green (Active): Credentials (medical licenses, CITI GCP certificates, CVs) are valid for more than 60 days.
    • Yellow (Expiring Soon): The credential expires within 30 to 60 days, indicating that coordinators should request updated documentation.
    • Red (Expired): The credential has lapsed; the platform prevents the individual from signing new study documents until an updated credential is uploaded.
  • Inspection Binder Export Package: When preparing for a regulatory inspection or closing a study, coordinators click Export Binder to produce a standardized, searchable PDF binder with embedded navigational bookmarks, document indices, and certification manifests formatted for regulatory submission.

Troubleshooting

When operating Florence eBinders across research sites, teams may encounter technical or configuration issues. Below are verified resolution steps for common operational challenges:

  • Florence ePrinter Driver Connection Error: If the Florence ePrinter hangs, fails to connect to the cloud environment, or displays a Destination Unreachable error, verify that the Florence background helper service is running on the workstation. Open the system tray, right-click the Florence icon, and select Check Connection. If communication fails, restart the Windows Print Spooler service via services.msc, verify that enterprise firewall rules permit outbound HTTPS traffic over port 443 to *.researchbinders.com, and re-authenticate your institutional Single Sign-On (SSO) session.
  • Signing PIN Lockout or Forgotten Credentials: Entering an incorrect Florence signing PIN three consecutive times locks the signing capability to prevent unauthorized document execution. To restore access, click Forgot Signing PIN on the signature prompt. The system dispatches a secure verification link to your registered institutional email address. Follow the link, enter your primary password, complete two-factor authentication, and establish a new six-digit PIN.
  • External Monitor or Auditor Cannot View Binder Folders: When an external CRA reports that specific study folders are invisible during a remote monitoring visit, navigate to Binder Settings → Permissions. Ensure that the monitor’s account is active and mapped to the External Monitor role. Check whether individual folder permissions have been restricted to Internal Study Team Only or flagged as confidential (such as unblinded pharmacy records). Adjust the folder-level visibility toggle to Monitor Accessible and confirm the monitor’s access window dates.
  • CTMS (OnCore) Synchronization Failure: If a newly approved protocol or study team member fails to sync from the institution’s CTMS into Florence eBinders, inspect the protocol integration identifier. Ensure that the protocol number and IRB number in OnCore match the Florence binder metadata exactly, with no leading or trailing whitespace. If synchronization remains stalled, trigger a manual re-sync through the institutional CTMS integration interface or contact the site CTMS operations office.
  • PDF Flattening and Fillable Form Artifacts: Uploading interactive, fillable PDF forms directly into eBinders can occasionally cause signature field corruption or rendering errors. To resolve this, open the source document in a standard PDF viewer, select Print to PDF to flatten all interactive form fields into standard vector layers, and re-upload the flattened copy to Florence.

Free alternatives

While enterprise clinical research centers often implement dedicated platforms like Florence eBinders, academic teams conducting investigator-initiated trials or pilot research frequently evaluate free, open-source, or existing institutional tools to manage trial documentation. The table below compares Florence eBinders with common alternatives across core regulatory and technical criteria.

Platform Primary Research Focus 21 CFR Part 11 Audit Trail Native Electronic Signatures Remote Monitor Portal Licensing Model
Florence eBinders Electronic Investigator Site File (eISF) and regulatory management Native, tamper-evident audit trails compliant with Part 11 and ICH GCP Dual-factor PIN-based digital signatures with completion certificates Dedicated, role-scoped CRA/monitor portal with redaction controls Commercial enterprise SaaS; institutional access through CTSC/CTSI programs
REDCap File Repository and e-Consent Clinical data collection, electronic survey administration, and consent Detailed project logging; Part 11 compliance requires institutional validation Native e-Consent framework with signature capture and PDF archival Customizable user rights; lacks specialized external CRA monitor workspace Free non-commercial academic license via REDCap Consortium
Nextcloud Community Edition Self-hosted research file sync, collaboration, and data storage File activity app tracks changes; requires hardening for regulatory audits Requires integration with third-party digital signature plugins Public sharing links with password protection and expiration dates Free, open-source software (AGPLv3)
Institutional Microsoft SharePoint General institutional intranet document management and storage Standard version history; requires compliance center configuration for audit holds Requires external digital signature integration (e.g., Adobe Sign or DocuSign) Guest access links governed by institutional Azure AD/Entra ID policies Included in standard academic Microsoft 365 enterprise agreements

FAQ

What is the difference between an eISF and Florence eBinders?

An electronic Investigator Site File (eISF) is the regulatory concept and operational structure defined by international standards (ICH GCP E6) to maintain essential trial documents at a research site. Florence eBinders is a proprietary software platform developed by Florence Healthcare that implements an eISF, providing digital folder structures, Part 11-compliant electronic signatures, and remote CRA monitoring tools.

How does Florence eBinder ensure FDA 21 CFR Part 11 compliance?

Florence eBinders incorporates administrative and technical safeguards required under 21 CFR Part 11, including secure user authentication, role-based access permissions, unalterable system-generated audit trails with UTC timestamps, dual-factor authentication (password plus signing PIN) for electronic signatures, and automated generation of cryptographic signature certificates of completion.

Can external monitors and CRAs access Florence eBinders remotely?

Yes. Florence eBinders provides a dedicated remote monitoring portal. Principal Investigators and site coordinators can grant clinical research associates (CRAs), CRO monitors, and sponsor representatives temporary, role-scoped access to review essential documents and participant binders. The platform includes built-in redaction tools to protect patient health information (PHI) and task assignment features to resolve monitoring queries without requiring physical travel to the site.

What is the Florence ePrinter and how is it used?

The Florence ePrinter is a secure virtual print driver installed on a user workstation. It allows clinical research staff to “print” digital documents directly from electronic health records (EHR), CTMS databases, laboratory reporting portals, or web browsers into designated study folders within Florence eBinders. This eliminates the need to download unencrypted files to local desktops or scan paper printouts.

How does profile document distribution streamline credential management?

In traditional paper environments, when an investigator renews their medical license or CV, copies must be physically placed into every active study binder. In Florence eBinders, the coordinator uploads the updated credential once to the investigator’s central profile binder. The system automatically pushes the updated document across all study binders associated with that investigator, updating the audit trail and resetting compliance expiration clocks simultaneously.

Sources

  • Florence Healthcare. Florence eBinders: Electronic Investigator Site File and Participant Binder for Research Sites. Vendor Platform Overview. URL: https://www.florencehc.com/products/ebinders/. Accessed November 10, 2026.
  • UC Davis Health Clinical and Translational Science Center (CTSC). Florence eBinders Overview and Guidelines. Clinical Trial Management System Operations. URL: https://health.ucdavis.edu/ctsc/area/ctms/florence-ebinders. Accessed November 10, 2026.
  • UC Davis Health Clinical and Translational Science Center (CTSC). Florence eBinder Training and Access. Standard Operating Procedures. URL: https://health.ucdavis.edu/ctsc/area/ctms/florence-ebinder-training-and-access. Accessed November 10, 2026.
  • Medical College of Wisconsin (MCW) Office of Research. Research Training Toolboxes: Florence eBinders. Clinical Research Systems. URL: https://www.mcw.edu/departments/research-training/toolboxes/florence. Accessed November 10, 2026.
  • U.S. Food and Drug Administration. Code of Federal Regulations Title 21, Part 11: Electronic Records; Electronic Signatures. Government Publishing Office. Technical Reference.
  • International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH). ICH Harmonised Guideline: Integrated Addendum to ICH E6(R1): Guideline for Good Clinical Practice E6(R2). Section 8: Essential Documents for the Conduct of a Clinical Trial. Standards Reference.

Follow CASRAI

Research-administration guidance, standards updates and independent tool reviews.

Ask CASRAI · free to try

Ask about Florence eBinder: Clinical Research eISF Guide

2 free questions a day, no account.

An AI assistant for research: funder rules, compliance, methods and publishing. It links the sources behind its answers and labels answers that come from a web search.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays open to read, with no account and no card.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →