MedCo Technical Documentation
GithubDocker HubMedCoLDS
v2.0.1
v2.0.1
  • Home
  • Releases
  • For System Administrators
    • Requirements
    • Deployment
      • Local Test Deployment
      • Network Deployment
      • Configuration
        • Passwords
        • Keycloak
        • Setting Authorizations
        • HTTPS Configuration
        • Configuring SwitchAAI Authentication
    • Data Loading
      • Synthetic SPO Data
      • v0 (Genomic Data)
      • v1 (I2B2 Demodata)
    • Command-Line Interface (CLI)
    • Network Architecture
    • Common Problems
  • For Developers
    • Local Development Deployment
    • System Architecture
    • Description of the default test data
    • Database
    • Live Demo
    • Release a new version
  • For users
    • MedCo Live Demo Tutorial
Powered by GitBook
On this page
  • External Entities
  • Firewall Ports Opening

Was this helpful?

Export as PDF
  1. For System Administrators

Network Architecture

PreviousCommand-Line Interface (CLI)NextCommon Problems

Last updated 4 years ago

Was this helpful?

External Entities

Entities that need to connect to a machine running MedCo can be categorized as follow:

  • System administrators: Persons administrating the MedCo node. Likely to remain inside the clinical site internal network.

  • End-users: Researchers using MedCo to access the shared. Likely to remain inside the clinical site internal network.

  • Other MedCo nodes: MedCo nodes belonging to other clinical sites of the network.

Firewall Ports Opening

The following ports should be accessible by the listed entities, which makes IP address white-listing possible:

  • Port 22, 5432 (TCP): System Administrators

  • Port 80 (TCP): End-Users (HTTP automatic redirect to HTTPS (443))

  • Port 443 (TCP): System Administrators, End-Users, Other MedCo Nodes

  • Ports 2000-2001 (TCP): Other MedCo Nodes

MedCo Network Architecture