Skip to main content

System Requirements

This document outlines the minimum and recommended system requirements for deploying and running MedFeed in your healthcare environment.

Server Requirements​

Minimum Requirements​

Backend Server (bl-engine)​

  • CPU: 2 cores, 2.4 GHz
  • RAM: 4 GB
  • Storage: 50 GB SSD
  • Network: 100 Mbps
  • OS: Ubuntu 20.04 LTS or CentOS 8+

Frontend Server (app)​

  • CPU: 2 cores, 2.4 GHz
  • RAM: 2 GB
  • Storage: 20 GB SSD
  • Network: 100 Mbps
  • OS: Ubuntu 20.04 LTS or CentOS 8+

Backend Server (bl-engine)​

  • CPU: 4 cores, 3.0 GHz
  • RAM: 8 GB
  • Storage: 200 GB SSD
  • Network: 1 Gbps
  • OS: Ubuntu 22.04 LTS

Frontend Server (app)​

  • CPU: 4 cores, 3.0 GHz
  • RAM: 4 GB
  • Storage: 50 GB SSD
  • Network: 1 Gbps
  • OS: Ubuntu 22.04 LTS

[Screenshot placeholder: Server architecture diagram]

Database Requirements​

MongoDB​

  • Version: 6.0 or higher
  • RAM: 8 GB minimum, 16 GB recommended
  • Storage: 100 GB minimum, 500 GB recommended
  • IOPS: 3000 minimum for production workloads

Redis Cache​

  • Version: 7.0 or higher
  • RAM: 2 GB minimum, 4 GB recommended
  • Storage: 10 GB for persistence

[Screenshot placeholder: Database configuration interface]

Software Dependencies​

Runtime Environment​

  • Node.js: v22.14.0 (backend), v18+ (frontend)
  • npm: v9.0 or higher
  • PM2: v5.2.0 or higher (for production)

Development Tools (Optional)​

  • Git: v2.30 or higher
  • Docker: v20.10 or higher
  • Docker Compose: v2.0 or higher

Network Requirements​

Bandwidth​

  • Minimum: 10 Mbps per concurrent user
  • Recommended: 25 Mbps per concurrent user
  • Voice Processing: Additional 5 Mbps per active voice session

Ports​

  • HTTP: 80 (redirect to HTTPS)
  • HTTPS: 443
  • Backend API: 3000 (internal)
  • Frontend: 3001 (internal)
  • MongoDB: 27017 (internal)
  • Redis: 6379 (internal)

[Screenshot placeholder: Network topology diagram]

Security Requirements​

SSL/TLS​

  • Certificate: Valid SSL certificate from trusted CA
  • Protocol: TLS 1.2 minimum, TLS 1.3 recommended
  • Cipher Suites: Strong encryption only

Firewall​

  • Inbound: Only ports 80, 443, and SSH (22) from authorized IPs
  • Outbound: HTTPS (443) for external API calls
  • Internal: Database and cache ports restricted to application servers

Compliance​

  • HIPAA: Required for healthcare data
  • SOC 2: Recommended for enterprise deployments
  • GDPR: Required for EU patient data

Client Requirements​

Web Browsers (Desktop)​

  • Chrome: v100 or higher (recommended)
  • Firefox: v95 or higher
  • Safari: v15 or higher
  • Edge: v100 or higher

Mobile Browsers​

  • iOS Safari: v15 or higher
  • Chrome Mobile: v100 or higher
  • Samsung Internet: v16 or higher

Device Specifications​

  • RAM: 2 GB minimum, 4 GB recommended
  • Storage: 1 GB available space
  • Network: 4G/LTE or WiFi connection

[Screenshot placeholder: Browser compatibility matrix]

Audio Requirements​

Microphone Specifications​

  • Quality: 16-bit, 44.1 kHz minimum
  • Type: USB or 3.5mm headset microphone recommended
  • Noise Cancellation: Preferred for clinical environments

Audio Processing​

  • Codec Support: WebM, MP3, WAV
  • Real-time Processing: WebRTC compatible browser
  • Bandwidth: 64 kbps minimum for voice transmission

Integration Requirements​

EMR Systems​

  • HL7 FHIR: R4 compatibility
  • API Access: RESTful endpoints
  • Authentication: OAuth 2.0 or API keys

Third-party Services​

  • AWS S3: For file storage
  • SMTP Server: For email notifications
  • SMS Gateway: For mobile notifications (optional)

[Screenshot placeholder: Integration architecture diagram]

Scalability Considerations​

Concurrent Users​

  • Small Hospital: 50-100 users
  • Medium Hospital: 100-500 users
  • Large Hospital: 500+ users

Performance Targets​

  • Response Time: Less than 2 seconds for API calls
  • Voice Processing: Less than 5 seconds for transcription
  • Uptime: 99.9% availability

Load Balancing​

  • Application: Multiple backend instances
  • Database: MongoDB replica sets
  • Cache: Redis clustering

Backup Requirements​

Data Backup​

  • Frequency: Daily incremental, weekly full
  • Retention: 30 days minimum, 1 year recommended
  • Location: Off-site or cloud storage

System Backup​

  • Configuration: Version controlled
  • Application: Automated deployment scripts
  • Recovery Time: Less than 4 hours RTO, less than 1 hour RPO

[Screenshot placeholder: Backup configuration interface]

Monitoring Requirements​

System Monitoring​

  • CPU Usage: Less than 80% average
  • Memory Usage: Less than 85% average
  • Disk Usage: Less than 90% capacity
  • Network Latency: Less than 100ms internal

Application Monitoring​

  • Error Rate: Less than 1% of requests
  • Response Time: 95th percentile less than 3 seconds
  • Availability: 99.9% uptime

Health Checks​

  • Application: Every 30 seconds
  • Database: Every 60 seconds
  • External Services: Every 5 minutes

Disaster Recovery​

Recovery Objectives​

  • RTO: 4 hours maximum
  • RPO: 1 hour maximum
  • Data Loss: Zero tolerance for patient data

Backup Sites​

  • Hot Standby: Real-time replication
  • Warm Standby: Daily synchronization
  • Cold Standby: Weekly backup restoration

For detailed installation instructions, see the Installation & Setup Guide.