...
The ClinSpark Agent is a patented separate / companion application to ClinSpark that enables deep integrations between the web application and peripheral systems running a Microsoft Windows operating system. The Agent application runs on a local user’s desktop and allows integration with devices such as Zebra label printers, ECG devices, vital sign machines, high precision scales, chroma meters, and much more.
...
Prerequisites
...
Microsoft Windows 10 or later
Minimum 4 GB RAM
Minimum 1 GB hard drive space
Downloading the Agent
Controlled access to the Agent installer MSI files are available to registered users in our Service Desk support portal.
...
The Agent Window Installer package (MSI) is provided via a protected ZIP directory. The MSI package is intended for use on a Microsoft Windows computing device. More details about recommended computing devices for Agent use can be reviewed here: Computing Devices
The decrypt password for the ZIP directory is 0214.
...
The Agent communicates with ClinSpark web servers using HTTPS on port 8070, and other device interfaces using TCP/IP network communication protocol. Sites that enforce strict network policies may restrict these communications over this port, which could lead to issues with certain features in ClinSpark/Agent that communicate through web services.
When the Agent is installed and run for the first time, Windows may prompt users with a message asking that network connections be allowed through the Agent. This must be accepted/allowed in order for the web communications to occur successfully.As a
Sites should verify that network connections for the Agent are allowed through Windows Firewall, and all necessary traffic ports. These settings can be configured within the Control Panel.
...
As an additional troubleshooting step, site administrators can confirm that the web socket connection is active while the Agent is running by visiting https://localhost:8070/ssl in a web browser. The confirmation of an ‘Ok’ ‘OK’ message in the browser window will indicate that the Agent is running properly and able to send/receive communications.
After that, further troubleshooting steps can should be taken on the local PC and sites to review network and firewall configurations, ultimately to determine if communications inbound/outbound are allowed for the Agent.
Browser Extension Conflicts
Users may have browser extensions installed that interfere with communications that must take place between ClinSpark/Agent for interface workflows. More details on that port via the Agentbrowser extensions are here: https://foundryhealth.atlassian.net/wiki/spaces/DOCS/pages/3700260899/Overview#Browser-Extensions
If users are unable to invoke device workflows, they should check to see if extensions are part of the cause. Using Chrome Developer tools for example, errors like the following may be present in the console:
...
In this example, a browser extension is blocking interactions between browser and the Agent, forcibly closing connections. This is accompanied by this message in ClinSpark:
...
This condition is symptomatic of ClinSpark being unable to communicate with the Agent on the local PC.
We’ve seen this observed with browser features/extensions that act as wide-spectrum content blockers (like uBlock, AdBlock, etc). Additionally, certain endpoint protection services that enterprise IT enforce on site machines may also cause this condition to occur if they are reporting communications between ClinSpark (browser) and Agent (local PC) as a false positive.
Device Dependencies on Visual C++ Runtime 2013
...