HealthCast

In addition to the client-side QwickACCESS install, QwickACCESS requires server-side software to function. You may choose to use either QwickACCESS Server or HC ProxAuth Server as the server-side software depending upon the type of your deployment.

QwickACCESS Server

QwickACCESS Server provides proximity badge services to QwickACCESS clients. QwickACCESS Server stores proximity cards and associated user credentials. QwickACCESS Server also provides authentication services to QwickACCESS clients. Authentication services are needed to validate user credentials when a user registers their badge, or when a user authenticates their badge. QwickACCESS Server is easy to setup and configure. QwickACCESS Server 2.6.x (and above) can be configured to use either an embedded database (for small to medium-sized deployments) or a Microsoft SQL Server database (for large to enterprise-sized deployments).

For more information about QwickACCESS Server, including installation and configuration instructions, visit the QwickACCESS Server documentation home page and then select the QAS version that you have.

HC ProxAuth Server

Alternatively, you may choose to use HC ProxAuth Server to provide proximity badge and authentication services to QwickACCESS clients. HC ProxAuth Server is recommended when QwickACCESS will be installed in an organization that is using HealthCast's ExactAccess product. Follow the link for more information about HC ProxAuth Server.

If you have questions regarding badge features, functions, and options surrounding badge functionality, please contact your HealthCast representative.