Before you run the installer
Gather what your PMS needs, on the server machine.
AVImark
Find the AVImark installation directory. You have the right one if it contains the file Client.V2$. Copy the path from File Explorer's address bar and keep it to hand.
Cornerstone
Nothing to gather.
Impromed
For a first-time install, make sure you have called Impromed support and had them create the read-only user on the Impromed SQL database. Otherwise, take the database username and password from ITGlue.
Open SQL Server Studio on the server and find out what the Impromed database is called. It is usually IMPROMED or Impromed, and the name is shown in the dropdown when you connect. Note the full server path as well, usually Impromed/Clinic-Name.
Type the database and server names exactly as SQL Server Studio shows them. This is the most common reason the Fetchit service refuses to start.
The database name, server, username and password go into the service configurator in the next step.
On the server machine
Run the Fetchit installer as administrator and select both Client and Service.
When it finishes, open File Explorer and go to:
C:\Program Files (x86)\Fetchit\Fetchit ServiceLaunch fetchitServiceConfigurator.
Fill it in. If this is misconfigured the service fails to start, or stops immediately after starting.
Server: broker.fetchitdata.cloud
Username: test
Password: test
Client ID: the client's internal identifier in Orion
Sync Interval: 60
Location: main
CRM: the clinic's PMS (None for a cloud PMS)
Phone System: None, unless they have a CallerID box
For a CallerID box:
IP: 0.0.0.0
Port: 3520Orion labels this value internal identifier. It is the same thing the configurator calls the client ID.
Click Save, then open the Services application and start the Fetchit Service.
The service syncs data from the PMS database up to Fetchit's servers in the background. On a clinic with a lot of history that takes a minute or two, and you can carry on while it runs.
If the setup is right, the service is still running a few seconds later. To be sure, open Event Viewer and go to Windows Logs > Application, then find Fetchit Service. No errors after the start event means you are clear.
On each workstation
Run the installer as administrator.
Complete the installation and launch Fetchit.
The installer adds Fetchit to the shell:common startup folder, so it launches at startup for any logged-in user. It will not launch at startup if the shortcut is set to run as administrator and the first user logged in at boot is not an administrator.
Fetchit appears in the Windows task bar tray.
Right click it and open Setup.
Enter the connection secret from the client's Orion page.
Select the full connection secret in Orion with Ctrl+A. A partial copy throws an error when you submit it.
Set the popup style to ezyVet, which is cosmetic and down to preference, then select the clinic's PMS from the dropdown. Leave the rest as it is and click Submit.
That completes the installation on the server and workstations for an on-premises PMS.
Verifying
Right click the tray icon and open History.
There should be entries here if the clinic has a phone system and this was not a first-time install.
To check the connection secret took, press Test Broadcast in Orion.
A red Broadcast 0 0000-0000 popup appears on screen. If it does not, the connection secret is wrong: enter it again, save, and retry.
Finally, call the clinic you have just installed for. You should see a popup for your own call, which proves both halves: the desktop application is working, and the phone worker, service or CallerID box is hearing calls. There is more you can do from that screen in Testing with Broadcast.