Types of Servers Required for AcuityLogic

Hosts application programming interfaces (APIs) between AcuityLogic and other systems, such as Demandforce, SolutionReach third-party recall and reminder services.

In small organizations, you can host other functions—such as searching, running batch jobs, and performing system maintenance—on the API server.

See API Server Requirements.

Runs batch jobs for integrations with insurance carriers, contact lens suppliers, and labs. You can also use it to perform general system maintenance.

Alternatively, you can run batch jobs on the API server to reduce costs.

See Batch Server Requirements.

Hosts the Eyefinity self-service conversion utilities.

See Conversion Server Requirements.

Provides online dashboards and drill-through reporting from separate systems, populated overnight with the previous day’s data.

This server can be used by organizations of any size.

See Dashboards Server Requirements.

Stores AcuityLogic data and logs, and contains the tempdb database.

See Database Server Requirements.

Stores electronic documents that you upload to AcuityLogic, such as PDF files and scanned images of patient referral letters and health benefit cards.

In single-server systems, you can store the documents in a web server on your local drive. In multiserver systems, the documents must be in a shared location.

See Network-Attached Storage Server Requirements.

Runs enhanced search functions to speed up searches for patients in large AcuityLogic systems. Most organizations with fewer than 500,000 patients do not need this.

To support enhanced searches, the server needs a Java Runtime Environment (JRE).

See Enhanced Patient Search Server Requirements.