Data Drill setup and configuration
Once the Dentrix Enterprise data drill has been installed, the data drill will be invalid by default as the SQL Connection Parameters must be entered to allow the Data Drill to connect to the Dentrix SQL Server entry (see sample image below). These Connection Parameters must be obtained and entered by the practice’s IT, or whoever manages their Dentrix Enterprise setup and SQL Servers.
Functions in the Data Drill:
Filter by: Allows the data drill to either see the patient database from all listed clinics, or only see patient’s from a specific location. “All Clinics” can be used as a catch-all, however some practices prefer DataGrabber to only locate patients from their location/clinic.
SQL Connection Parameters: Necessary to allow the Data Drill to connect to Dentrix Enterprise’s SQL Server. Without these, the data drill will not locate any patients and will not be valid.
Active Patients only: Unchecked by default. If checked, the Data Drill can only see patients marked as “active” within Dentrix.
Append middle initial to first name: Checked by default. Adds the patient’s middle initial to the first name field when bridging, and can be disabled if patients in Apteryx are mapped to exclude middle initial.
Column to use as patient ID: Allows user to specify which number is used by the Data Drill as the patient’s ID number. See https://planetdds.atlassian.net/wiki/spaces/DIKB/pages/edit-v2/3430318377#Determining-which-Column-to-use-as-Patient-ID
A sample valid Data Drill- note connection parameters are entered, and patients are being found in the database. If incorrect, it would show invalid or “0 patients found in the database.”
CDB Exception Errors
These errors occur if the SQL Connection Parameters are invalid, or need to be entered. If the SQL Connection Parameters are blank, or you are getting an error referencing invalid credentials or entries, have the practice’s IT enter the correct SQL Connection parameters then click “Test Connection.” A number of patients found in the database will be displayed if the parameters are valid.
Determining which Column to use as Patient ID
TBA - need screenshots/how to check which ID is which in Dentrix
If the Column to use as Patient ID is incorrect, duplicate patients will occur and existing patient charts won’t appear in the imaging software. During first time setup, its recommended to pull up a patient the office knows has existing images, and bridge that patient with each ID option checked until the patient’s existing record appears in order to find out which option is correct for now.
Known Working Sniffer Definition
The default Dentrix sniffer definitions for the patient chart may not find the patient records. The following may produce better results when using Dentrix Enterprise.
Sniffer not finding Published Application Window
Ensure the published app patient chart window is not full screen
Drag the sniffer crosshairs to the header window. When you do it will auto-populate the Search String information needed. You need to modify the Name Search String to only include the beginning of the search string that is repeatable. In the example below, it would read “Dentrix Chart - (Doe, John) …” and you would need to delete everything after “Dentrix Chart -”
Build a new Extraction definition that is able to read the patient info
Dentrix Enterprise DRL Configurations Keep Resetting
If the settings inside the Dentrix Enterprise DRL will not stick/keep resetting:
Try configuring a mapped drive path to the computer for the DG install location.
Verify that all config files and folders have full permissions granted.
Set the parameters, close DG and then make the main Dentrix DRL config file read-only.
OBDC Setup/Information
NOTE: do not use the below unless completely necessary - ODBC data sources should be configured by the office’s IT, and the correct OBDC data source should exist for Dentrix Enterprise by default.
**IF THE BELOW ODBC STEPS DO NOT WORK, THE OFFICE NEEDS TO IDENTIFY WHAT INFO THEY NEED TO ACCESS THEIR DB**
If you have a connection issue when trying to find the SQL instance through ODBC to the Dentrix server, make sure that sad Pipes is enabled in SQL configuration.
If the office can get their ODBC to connect, it should reflect the same access in the datadrill
Hit windows key>search and select ODBC
Navigate to the System DSN>Select Add
Select SQL Server
Fill out the Name field with anything and hit the Server Dropdown arrow and let it load
Document the Server name that populates as this will be used in the SQL connection Parameters in the DRL
Select the applicable Server and hit next
Select With SQL Server authentication using a login ID and password entered by user option
Have the office fill in their info here (example: This office in the screenshot below uses "Enterprise" as the login ID)
Hit next
If this successfully proceeds to the next tab it should work in the DRL options
Sample Credentials Shown below
Offices using ODBC Drivers not native to PC
An office IT may feel obligated to show that ODBC Server 11-17 can connect even though the native ODBC Does not
The DRL uses the connection through the true SQL Server ODBC connection, not through the ODBC 11-17 driver. So this would be an issue related to the native ODBC on the computers that cannot connect