Progeny Network Configuration Options

The following configurations are the most common used to deploy Progeny. These configurations cover all products available from Progeny Software.

Configuration 1: Standard Network (No Web Server)

Local Users

Progeny Database Server

Perimeter Firewall

External Users (Optional, recommend VPN)

This configuration is for customers who purchase the Progeny FAT (Windows) Client and the Progeny Server. This is used to allow multiple FAT Clients to simultaneously access the same database. *NOTE: Without the Progeny Server, databases can only be accessed by one FAT Client at a time.

Configuration 2: Progeny Web with No External Access

Web Client Access Only Progeny Web Client Progeny Admin Access Web Client for Daily Use FAT Client Access for Database Configuration Progeny Admin Standard User

Progeny FAT Client

Server Access for Database and Client Maintenance IT Admin Progeny Database Server + Web Server
This configuration is for customers who have purchased the Progeny Web Server. Because there is no external access, there is no need to segregate the Database and Web Servers (everything resides behind the firewall). This configuration includes two (2) Progeny FAT Clients one for database configuration and maintenance (installed on the Progeny administrative users desktop) and one for security and user maintenance (installed on the server). All other users will have access to the browser-based Web Client.

Configuration 3: Progeny Web with External Access

Progeny FAT Client

FAT Client Access for Database Configuration Progeny Admin

Web Client Access For Daily Use Progeny Web Client Web Client Access Only

Standard User

External Users

DMZ
Web Client Access Only Progeny Database Server FAT Client Access for Database Maintenance IT Admin Perimeter Firewall Progeny Web Server Web Server Access for Questionnaire Maintenance

This configuration is for customers who have purchased the Progeny Web Server. The design is essentially the same as Configuration 2, except that users will be allowed to access the Progeny Web Client from outside the company network. Since this external access by users is allowed, the Web Server will need to be segregated from the Database Server for security. Most often, the Web Server is placed in front of the firewall in the DMZ. The Web Server is given a public IP address and URL, and is secured with an SSL certificate.

Configuration 4: Progeny Web with Family History Questionnaire

Progeny FAT Client

FAT Client Access for Database Configuration Progeny Admin

Web Client Access For Daily Use Progeny Web Client Web Client Access Only Patient At Home

Standard User

DMZ
Progeny Database Server FAT Client Access for Database Maintenance IT Admin Perimeter Firewall Progeny Web Server Web Server Access for Questionnaire Maintenance

Web Access To Questionnaire

This configuration is for customers who have purchased the Progeny Web Server and the Family History Questionnaire module, which allows patients to enter their own family history data which is then entered into the Progeny database. The design here is identical to Configuration 3, except that Progeny Web Client users will share the external access with patient entry.