Fetchit

Switch to dark theme

Practice management

Gathering PMS settings

Collect the API keys, clinic IDs and database details Fetchit needs from the clinic's practice management software before you configure Orion.

Which of the two classes of PMS the clinic runs, and what each one wants you to collect.

  • pms
  • crm
  • credentials
  • integration
Author
Schultz Technology IT
Owner
Schultz Technology
Updated
Applies to
Fetchit 1.4.0 to 1.6.0
Reading time
2 min
Level
intermediate
For
IT technicians
Prerequisites
Administrator access to the clinic's PMS

With the phone system configured, the next step is to gather the credentials Fetchit needs from the clinic's practice management software. You enter them into Orion in the PMS settings step.

Clinics run one of two classes of PMS:

  • On-premises, installed on servers and workstations at the clinic.
  • Cloud based, reached through an online portal in a browser.

For the cloud systems, there are credentials to collect from a portal so Fetchit can integrate with them. The pages below cover each one and what it wants.

AVImark and Cornerstone need nothing here

If the clinic runs AVImark or Cornerstone, there is nothing to collect and nothing to enter in Orion. Skip straight to the desktop app installation. Impromed is on-premises too, but it does have a step; see below.

The systems

  • Impromed. A read-only SQL user, created by Impromed support.
  • ezyVet. An API Partner integration, downloaded as a credentials file.
  • Shepherd. The clinic ID, plus the Fetchit data connection enabled.
  • Digitail. A login for the clinic's Digitail account.
  • Rhapsody. The clinic ID, read out of the portal URL.
  • Vetspire. An API token.
  • VETport. API base URL, username and password from their support team.
  • DaySmart. A service account staff member you create.
Record the credentials

Everything you collect on these pages goes into the client's ITGlue entry as you go.