Skip to content

Hybrid File Transfer Solution

Overview

The Hybrid File Transfer Solution enables secure, bidirectional file exchange between on-premises laboratory systems and external partners. It bridges an on-premises file share with cloud object storage, and exposes a managed SFTP endpoint so external collaborators can exchange files without requiring direct network access into the internal environment.

In summary, the solution provides for:

  • Laboratory metadata generated on-premises to be made available to authorized external partners.
  • External partners to submit files that internal laboratory users can consume.

Both directions are handled automatically, with strict isolation maintained between internal and external users — each is restricted to its own directories, and neither can access the other's data.

Background and Rationale

Laboratory workflows often generate operational files — sample sheets, run sheets, instrument outputs — that need to move reliably between on-premises instrumentation, cloud storage, and external collaborators or downstream processing systems.

This solution consists of:

  • A standard file share on the lab side, so no special client software or workflow changes are needed for lab users or instruments.
  • A fully managed SFTP endpoint for external partners, removing the need to operate a dedicated external-facing server.
  • Automated synchronization between the two, so files appear on each side without manual intervention.

Intended Audience

  • Laboratory users and instrument systems that need to publish operational files for external consumption, or consume files submitted by external partners.
  • External partners and collaborators who need a simple, secure way to exchange files without gaining broader network access.
  • Hybird File Transfer Solution Team responsible for onboarding new labs or partners onto the shared file exchange model.

Current Status

This solution is currently implemented as a Minimum Viable Product (MVP). It demonstrates the feasibility of the architecture and validates the core design assumptions around access control and isolation. Broader production-readiness work (high availability, full monitoring rollout, formal support processes) is planned as a follow-on effort and is outside the current scope.

Document Structure

This documentation is organized as follows:

  • Purpose and Features — what the solution does and its key capabilities.
  • How to Use It — practical steps for lab users and external partners.
  • High-Level Architecture — the components involved and how they fit together.
  • Example Use Cases — real-world scenarios this solution supports.