TigerView INI File Bridging w/ Thumbnail Integration Instructions
TigerView features an enhanced method of practice management software (PMS) or Electronic Medical Record (EMR) software integration that allows more information to be passed to TigerView than is capable with the standard TigerView command line interface.This enhanced method uses a combination of an application command line parameter and a text file to create and locate records in the TigerView database. When TigerView is launched with the command line parameter "SLAVE" it looks into the Windows directory for a file named "tiger1.ini". TigerView reads the information contained in "tiger1.ini" and uses it to locate an existing record or to create a new record. It is the responsibility of the PMS or EMR application to create and fill out the "tiger1.ini" file before launching TigerView. This is different than a predecessor product, TigerView Classic.
This builds upon the standard INI File bridge and allows your PMS/EMR to specify a folder path where 24 bit jpeg thumbnail images will be copied for direct displaying and linking in your application.
Note: This method of bridging is currently only supported in TigerView Cloud product.
Please refer to the flow chart shown in figure 1 below.
Practice management software fills out the required fields and any optional fields in the "[Slave]"section of Tiger1.ini. (see figure 2)
Practice management software starts TigerView using the following command line: "drive:\path\tiger1.exe" SLAVE
TigerView starts with no splash screen. The designated patient is selected or created using the information provided in the tiger1.ini file.
TigerView deletes the patient information form the tiger1.ini file.
Figure 1
Fill out the [Slave] section of the tiger1.ini file as shown in figure 2: (section and key names are not case sensitive, and can be in any order.)
| [Slave] | Data Type | Required Format | Required | |||
| ThumbFolder= | Alpha/Num | Any valid windows folder path, network drive path, or UNC path | Yes | |||
| LastName= | Alpha/Num | spaces, hypens, apostrophes accepted | Yes | |||
| FirstName= | Alpha/Num | spaces, hypens, apostrophes accepted | Yes | |||
| ProviderLastName= | Alpha | spaces, hypens, apostrophes accepted | No | |||
| ProviderLastName= | Alpha | spaces, hypens, apostrophes accepted | No | |||
| PatientID= | Alpha/Num | No | ||||
| PatientSSN= | Num | xxx-xx-xxxx or xxxxxxxxx | No | |||
| SubscriberSSN= | Alpha/Num | xxx-xx-xxxx or xxxxxxxxx | No | |||
| Gender= | Alpha |
(Enumerated value. Must be one of the Options listed below)
"MALE" "FEMALE" "MALE - NEUTERED"* "FEMALE - SPAYED"* |
No | |||
| DOB= | Date | Valid date format ie. mm/dd/yyyy | No | |||
| ClaimID= | Alpha/Num | No | ||||
| AddrStreetNo= | Alpha/Num | No | ||||
| AddrStreetName= | Alpha/Num | No | ||||
| AddrSuiteNo= | Alpha/Num | No | ||||
| AddrCity= | Alpha/Num | No | ||||
| AddrState= | Alpha | No | ||||
| AddrZip= | Num | No | ||||
| PhHome= | Alpha/Num | No | ||||
| PhWork= | Alpha/Num | No | ||||
| Email= | Alpha/Num | No | ||||
| PetName=* | Alpha/Num | Yes | ||||
| Breed=* | Alpha | No | ||||
| Species=* | Alpha | Yes | ||||
| * Applicable only in Veterinary mode | ||||||
Figure 2
LastName, FirstName, ThumbFolder are required fields. All other fields are optional (except in Veterinary mode where Species and Pet Name is also required). In Veterinary mode, First and Last name refer to the Owner's name.
TigerView will create subfolders inside the specified thumbnail folder for each Patient. These subfolders will be named using the Patient's ID (if available), or the patient's name in the format of LastName_FirstName (or LastName_FirstName(PetName) in Veterinary mode). Simply check these these folders for *.jpg files when displaying a Patient's record to the user.
View our Direct Thumbnail bridge guide on how to use the thumbnails displayed in your PMS/EMR to open the full-sized image in our viewer.
TigerView uses the PatientID field to determine whether the patient already exists in the database. If the ID matches an ID in the database, the patient is selected. If the ID doesn’t match, TigerView will attempt to match on an exact first and last name. If no match is found the patient is created.
If optional patient information is sent over that does not match the information already in a patient record, the new information being passed will not be updated in TigerView.
Use the PatientSSN field to send over the SSN belonging to the patient. Use the SubscriberSSN to send over the SSN of the Insured.
Provider First Name and Last Name must both be passed to be accepted. Both names need to match the Provider information in TigerView Administration exactly.
Provider First Name and Last Name will only work with TigerView Professional versions 7.0.18 or later.