Step 1: Request an API key from Vetspire
Contact Vetspire Support and request an API key for Instinct.
Note: It may take up to a week for Vetspire to provide the API key.
Step 2: Export your Vetspire user IDs
Log in to Vetspire as an Administrator.
Select More → Users. The Users page lists the User ID for each staff member at the location selected. Verify the selected location in the upper-left corner.
Export the list of Vetspire users.
Note: Super Admins may not appear in the user list, since they aren't associated with a location. If your practice has any Super Admins set up in Vetspire, add them to the exported list of users manually.
Step 3: Find your Vetspire Location ID
Log in to Vetspire as an Administrator.
Select More → Locations.
Click your practice location in the list. If you don't see the location you're looking for, contact Vetspire Support for assistance.
Find the Location ID field and make note of the number.
Step 4: Send your API key, Location ID, and user export to Instinct
Email the Vetspire API key, the Vetspire user ID export file, and the Location ID to [email protected].
Test and Verify Your Instinct Installation
After Installing the Instinct Client App and connecting to Vetspire, confirm everything is working correctly before go-live.
What to expect before your servers are live
The Instinct team usually brings up your servers and uploads your practice's data 5 to 7 days before go-live, if not sooner. Once the servers are up, you can officially log into Instinct.
If you're testing the app before the servers are up, you'll see Instinct's Auto-Login screen stating that Instinct needs to authenticate your practice. This is expected behavior if it appears before your servers are live.
What to do if the Auto-Login screen appears after go-live
If you see the Auto-Login screen after your servers are available, check whether the Instinct app has access to the token file you set up.
Note: If you still have trouble logging into Instinct after checking your token file, contact the Support Team at [email protected].
Tests the Instinct team runs before go-live
Once your Instinct servers are up and the first client install is complete, the Instinct team verifies that the app can connect to the Instinct server successfully by testing:
Basic functions of the Instinct App
Whether patient data is being updated via Vetspire
Auto-update of the Instinct Client App
Ancillary items, such as confirming readability and screen resolution
Vetspire Patient Check-In and Check-Out Status Mapping
Instinct checks a patient in when their Vetspire status is one of the following:
Check In
Admitted
In Progress
Daycare
MedBoard
Pending
Note: For new visits, the Admitted status places the patient on the IP Board. Checked In, In Progress, Daycare, MedBoard, and Pending place the patient on the OP Board.
Statuses that check a patient out
Instinct checks a patient out when their Vetspire status is one of the following:
Completed
Checked Out
No Show
Cancelled
Confirmed
Planned
Wait List
Checking Out
Frequently asked questions
How long does it take to get an API key from Vetspire?
It may take up to a week for Vetspire to provide the API key after you request it.
Where do I find my Vetspire Location ID?
Select More → Locations in Vetspire, click your practice location, then find the Location ID field.
Is it normal to see the Auto-Login screen before go-live?
Yes. This is expected behavior if your Instinct servers aren't live yet.
Why isn't my patient showing on the Status Board?
Confirm the patient's Vetspire status matches one of the check-in statuses listed above. Instinct only checks in patients with a matching status.
Which board does a newly admitted patient appear on?
For new visits, the Admitted status places the patient on the IP Board.
Still need help?
Contact Instinct support via live chat or email [email protected].