Why PACS?
What are the key benefits for the user?
Enhanced Biosecurity
- Unique identification of samples
- Exact location traceability
- Full audit trails
- Configurable role-based access control
- Highly secure closed system
- Three tiers of database backup
Laboratory Efficiency
- Quick data retrieval
- Minimized operator errors
- Real-time analytics
- Quality control
- Reduced paperwork
- Biosurveillance support
Sustainability
- Turnkey solution
- Proven implementation approach (70+ sites)
- Rapid rollout (6-12 months)
- Sustainable training program
- User HelpDesk
- No license fees
System Features
Efficient Inventory Management
- Exact location of Aliquots
- Tracks all types of biological materials & tests
- Repository configuration
- ↠ Simple navigation
- ↠ Track available storage capacity
- ↠ Repository audit
- Sample and tests management
- Source-Material-Aliquot-Test traceability
- Barcode and QR-code technology
Information Security
- Highly secure closed system
- Configurable Role-Based Access Control (RBAC)
- Full audit trails & event logs for accountability
- Data encryption for data at rest and in transit
- Regular security updates and patch management
- Backup & recovery – 3 tiers of database backup including off-site backup
- Incident response protocols
- Compliance with security standards (ISO 27001, NIST)
Sample Identification and Barcoding
- Minimize operator errors
- Label designer
- QR codes and barcodes
Operations
- Batch data entry & processing
- ↠ Batch Material Registration
- ↠ Data import
- ↠ Validation checks to support data correctness
- Support for Biosurveillance Studies
- ↠ Powerful search engine
- ↠ Quick data retrieval
- ↠ Data export
- ↠ File attachments
- Customizable Forms
- ↠ Data entry forms
- ↠ Report forms
- ↠ Reference values
- Aliquoting, Subculturing, Movement, Material Usage
- Diagnostics and Tests
- Destruction and Transfer
- Inventory Audit
- Data export
- Multilingual application
Implementation Approach
From planning to successful integration of PACS in an organization’s daily lab routine.
Gradual transition of sustainment responsibilities from CTR to recipient laboratory according to a mutually agreed plan and schedule.
1
Planning
- Demonstration
- Site Survey
- Determination of system configuration
- Implementation plan approval
- Training coordination
2
Deployment
- Pre-deployment planning – site readiness, VAT exemption, logistics
- Hardware procurement & deployment
- PACS installation & configuration
- System connectivity testing
- System Operational Testing (SOT) & validation
- Post-deployment Maintenance & Support
3
Training
- Train-the-Trainer approach
- Classroom or remote/online training
- Training Materials provided
4
Commissioning
- Initial data entry (sample metadata and inventory)
- System customization (roles, permissions, workflows)
- Data import & validation (ensuring data integrity)
- Designation of cybersecurity roles & responsibilities
- System verification & acceptance testing
- Supporting Documentations
- ↠ PACS Application Standard Operating Procedure (SOP) specific for PACS site
- ↠ User and Administrator Manuals
- Cybersecurity Documentation
- ↠ PII Data
- ↠ Access Rights Governance Policy
- ↠ Acceptable Use Policy (AUP)
- ↠ Incident Response Plan (IRP)
- ↠ Contingency Plan (CP)
- ↠ Security Audit Procedures
Support Services
- HelpDesk
- Follow-up On-the-Job Training (upon request only)
System Requirements
Sizing Guide
DATABASE (SERVER/STANDALONE) INSTALLATION
| Site type | Total # of Aliquots | Desktop Clients | Operating System | DBMS | Cores | Memory (GB) | Storage Space Required (GB) 1 |
|---|---|---|---|---|---|---|---|
| Small dataset, a few desktop workstations | ≤400K | ≤ 10 | Windows Server 2025/2022 ; Window2 11/ 10 |
SQL Server 2019 (Express editions) | 4 | 4 | 50 GB (application files, data size and backup files) |
| Large dataset, small amount of desktop workstations | 400K – 1M 4 | ≤ 10 | Windows Server 2025/2022 ; Window2 11/10 |
SQL Server 2022 (Standard Edition) | 8 | 8 (for ≤ 400K aliquots) +1GB for each 100K aliquots |
20 GB (application files) + 2GB for each 100K aliquots for data size and backup files |
| Large dataset, large number of desktop workstations | 400K – 1M 4 | 10+ | Windows Server 2025/2022 ; Window2 11/10 |
SQL Server 2022 (Standard Edition6) | 8 (for ≤ 10 concurrent requests 5) + 2 cores for each 5 next concurrent requests |
16 (for ≤ 5 concurrent requests 5) + 4GB for each 3 next concurrent requests |
20 GB (application files) + 2GB for each 100K aliquots for data size and backup files |
1. Storage space doesn’t include space required for other software, e.g. DBMS or .Net Framework.
2. Operating systems Windows 11, 10 can only be used for the standalone installation of PACS database.
3. It is recommended to update SQL Server during the installation process.
4. The threshold of 1 million aliquots ensures optimal system performance. A larger dataset may affect system response times.
5. Concurrent user requests indicate users actively using the system simultaneously. Estimated number of concurrent requests ~ 10% of Desktop clients.
6. The Enterprise Edition can be installed for a large dataset and/or a large number of desktop clients.
Database Prerequisites
DATABASE (SERVER/STANDALONE) INSTALLATION – SOFTWARE PREREQUISITES 1
| Component | Requirement |
|---|---|
| .NET Framework | .NET Framework 4.5.2 |
| DBMS | SQL Server 2012/2014/2016/2017/2019 with latest available Service Pack (see editions applicable for different site types in the DATABASE (SERVER/STANDALONE) INSTALLATION section) |
| Network Software 2 | Supported operating systems for PACS have built-in network software. PACS uses the following network protocols for communication between PACS Database Server and desktop client: Named Pipes, TCP/IP |
| Virtualization 3 | PACS is supported in virtual machine environments |
1. This section does not contain prerequisites for other software, e.g. DBMS.
2. The configuration of network protocols is not required for PACS standalone installation.
3. Running PACS on a virtual machine is slower compared to when PACS is directly installed on a computer, because of the overhead of virtualization.
Desktop Clients Requirements
PACS DESKTOP CLIENTS REQUIREMENTS 1
| Component | Requirement |
|---|---|
| Operating System | Windows 10 / 8.1 / 8 / 7 SP1 |
| Processor | 2 GHz or faster |
| RAM | 4 GB |
| .NET Framework | .NET Framework 4.5.2 |
| Network Software | Supported operating systems for PACS have built-in network software. PACS uses the following network protocols for communication between PACS Database Server and desktop clients: Named Pipes, TCP/IP. |
| Report Viewer 2012 | Microsoft Report Viewer 2012, a prerequisite for PACS, includes controls for viewing reports, which are designed with Microsoft reporting technology. |
| Internet Software | Internet Explorer 7 or later, or another Internet browser is required for HTML Help |
| Hard Disk | 5 GB (including application files and patches) |
| Monitor | 1280 x 960 or higher resolution monitor |
| Supported barcode devices | • Barcode scanner • Zebra GC420T desktop printer |
| Recommended Software | • Antivirus Software • OpenOffice, LibreOffice or another Office Suite of the latest available version |
1. See requirements from PACS DATABASE INSTALLATION and DESKTOP CLIENT INSTALLATION sections when installing the PACS Standalone version.