Architecture
Genedata Screener is built upon classical 3-Tier architecture with rich clients, a central application server, and a database. This architecture ensures unmatched performance and scalability. As all client updates, system configurations, and customer specific integrations are provided via the central application server, Genedata Screener keeps maintenance and operational costs low. A typical Screener installation at an HTS service unit requires only a fraction of an FTE for regular operation and maintenance.
The Genedata Screener database stores the original data imported from the screening instruments and all results generated by the Genedata Screener application modules. All processing decisions and user annotations are captured, providing a fully documented trace for Genedata Screener results.
In addition, the database serves as a persistency infrastructure, which stores sessions and allows users to pause and continue data analysis any time.
Screener Application Server
Central and Scalable instance, facilitating all data flow and unifying all configurationsThe Genedata Screener Application Server is the hub between Genedata Screener modules and the Genedata Screener database, serving clients, transferring data, controlling access, and channeling communication. It centrally hosts all configurations and programmatic extensions, minimizing maintenance efforts.
Data import and export are customer-specific implementations of Genedata Screener Application Programming Interfaces (APIs). Genedata Screener comes with default integrations that enable operational setup in minutes. The APIs allow further integration between the IT infrastructure and the Genedata Screener system, relieving users from manual configurations or data transfers. APIs are well documented and versioned, guaranteeing efficient setup and operational stability.
Processing of screening data follows both scientific standards and company-specific business rules. Genedata Screener Data Processing APIs adapt to many calculations such as, normalization, fitting, IC50 determination, derived statistics, and company-specific rules. API implementations are centrally maintained on the application server for easy distribution and maintenance.

