Overview of Client Installation Process

The Prima application server must be completely installed before a client installation can be performed.

The Prima client installation can install up to five client applications, depending on the use case at each station. For a research setting, you may choose to install all. For a production oriented lab, you may only choose to install one.

Workstations
Used by the lab techs to perform the bulk of the standard workflow (printing, scanning, staining, etc.)
ControlPanel
For users with admin privileges, provides the ability to setup drop-downs, define workflow rules, etc.
LabManager
Gives lab managers the ability to handle QC problems, ok QC material, view lab metrics and more
Pathologist
Gives Pathologists the ability to view everything recorded with cases and studies and to make diagnoses
Label Template Creator
Provides the ability to create templates for printing within Workstations. Access to ControlPanel is needed in order for the settings to be used in the lab.

Client Workstations

As a general stance on supported versions of software, Fortelinea stays very much on top of using all new performance and security measures in new versions of software. This means newer versions are always better, as far as we are concerned.

Hardware Requirements

Hardware requirements can vary quite a bit from station to station, depending on which application the user will use.

Prima Workstations

Parameter Minimum Recommended
CPU 2.4GHz, 2 cores 3.4+GHz, 4 cores
Memory 4GB 8GB
Operating System Windows 10 Windows 10
Workstation Monitors 22 inch HD 27 inch HD touchscreen
LabManager/Pathologist Monitors 28 inch 4k 34+ inch 4k

Installing Features and Drivers

  • Ensure that .NET Framework 4.8 (an up-to-date OS should have this already) is installed on the application server
  • While not currently required, it would be smart to install .NET5 (an up-to-date OS should have this already), as it the current version and we will likely require it soon.

SSL Certificates

The Prima service sends out notifications to the clients over callback channels. While we attempt to limit the amount of sensitive information sent over these channels, we still recommend encrypting with an SSL certificate. Ensure that:

  • The certificate must match the name of the computer (this can be a vanity name, computer name or a wildcard)
  • Any workstation user account must have access/privileges to the private key
  • The cert should be signed by your CA or an outside trusted CA; the cert needs to be trusted by the server
  • The cert should be placed in LocalMachine\My of the certificate store
  • The cert should be at least 256 bit

Network Prep

The clients need to be able to communicate to:

  • The Prima application server on ports 9350-9355, 443
  • https://prima.fortelinea.com

Record Settings for Prima Installation

Before we run the Prima installer, you'll want to make sure you have the following:

  • The address of the Prima application server
    • Add a new Workstation entry in Prima via ControlPanel or the web app
    • Ensures correct tracking (barcode scans) and logging information
    • Shows up in a drop-down in the Prima installer

Troubleshooting and Extra Installation Info

Prima Website Logs
As long as the application has access to talk to our server (https://prima.fortelinea.com), we get and log a variety of detailed information on crashes, exceptions, and configuration warnings. Usually, the website logs are the first tool Fortelinea developers use when troubleshooting.
Event Viewer
The Windows Event viewer is a great place to look. Most serious logs end up here. Be sure to check under Application and System event logs.
File logs
There are times when exceptions don't make it to the event viewer due to a crash and the logs don't make it to our website. The fallback are textual log files which can be found at C:\ProgramData\FortelineaSoftwareSystems\Prima\Logs

Client Installation Checklist

  1. Know the address of the Prima application server
  2. Use ControlPanel or the web app to add a Workstation
  3. Ensure .Net Framework 4.8 is installed
  4. Ensure the client has a useable SSL certificate