Central Enterprise Management Tool (CEMT)
The Central Enterprise Management Tool (CEMT) allows Multiple Locations to use separate databases at each location, yet have a centrally located management tool to interact with all the databases.
Logging On to the CEMT
Search for Patients
Production and Income Report
- Every location must be on the same version of Open Dental.
- All offices need to be on a single VPN.
- If using the Middle Tier at each location for increased security, you could connect over the VPN or over https.
- If using One-Way Replication the CEMT tool should only connect to a local copy of the database, not the remote databases.
Updates: To prevent accidental updates of Open Dental when multiple locations potentially run different Open Dental versions, set an Update Server Name (also known as Middle Tier Server Name) in Miscellaneous Setup. This computer will be the one and only computer that has permission to execute updates.
How it Works
The CentralManager.exe is shipped and installed in the same Open Dental folder as
the main program. It connects to a mostly blank Open Dental database (e.g. dbcentral) that does not have any patient information or use most of the normal tables. It does have some of its own tables that are ignored by the ordinary Open Dental program. Before initial use, you must configure the CentralManagerConfig.xml file. See CEMT Setup.
To run the CEMT, run CentralManager.exe. After Logging On, the main window will open.
From this central location you can easily:
- Launch database connections.
- Search for Patients across multiple databases.
- Set up database connections.
- Check the database connection status and version in contrast to CEMT database version (upper right).
- Configure and sync security settings.
- Run a production and income report for multiple databases at once.
Central Manager Window
Below are descriptions of the options on the Central Manager window.
- Logoff: Log the current user out of CEMT and open the Log On window. CEMT Setup
- File, Change Password: Change the password for the currently logged on user.
- Connections: Set up database connections. CEMT Connections.
- Groups: Set up categories of database connections (useful for reporting).
- Security: Define security settings (users, user groups, permissions, and lock dates). See CEMT Security.
- Reports: Run a daily, montly, annual, or provider production and income report. See CEMT Production and Income Report.
Search Connections: Search connections for a Connection Name, Clinic or Provider. Enter text then click Refresh to update the list. The Connections list will update with connections that have matching results.
Connection Groups: Click a dropdown option to only view connections for a specific group. Set the default on the Connection Groups window.
Connection Tools: Before using a tool, select the database connection(s).
- Search Patients: Select the database connections, then click Patients. See Search for Patients.
- Sync: Sync CEMT Security information with selected database connections.
- Locks: Sync only lock dates. This will override any local Global Lock Dates.
- Security: Sync all security settings (user, user groups, permissions, and lock dates).
- Users: Sync only users, user groups, and permissions.
- Middle Tier Only: This option is only visible if Middle Tier connections show in the grid.
- Sync Manual: For first time set up only. Sync all security settings to the selected middle tier connections. Middle Tier server credentials are required.
Connections: Each connection already setup is listed, along with its version in relation to the CEMT database version.
- Double click a connection to launch a separate instance of Open Dental for that database. You will be logged on using your CEMT username and password. The launcher makes use of Command Line Arguments.
- Add: Click to add a new connection. See CEMT Connections
- Edit: Select a connection, then click to edit a connection.
- Refresh Connections: Click to show the database status in relation to the CEMT database for all connections currently listed.
- OK: Connection version matches CEMT database version.
- version x.x.x: If versions are different, the version of the connection is listed.
There is a problem connecting to the database.
- Not Checked: Connection status has not been checked yet.
- Automatically Log-On: If checked, when you launch a database connection, the user logged on to the CEMT will be automatically logged on to the launched connection using the same credentials. If unchecked, the Log On window will open so you can manually log on instead.
Problem: Version information is in red text after 'Refresh Connection'.
Solution: This means the Open Dental database is using an older version than the CEMT, and thus can't be synced with or connected to. The CEMT will not interact with the database until it is updated.
Problem: Name conflicts when syncing users (states which names are in conflict).
Solution: Rename the CEMT user using a unique user name. Because CEMT users never show up in the normal Open Dental interface, their username can be anything. For example, Open Dental user 'Sally', could use 'SallyCEMT' as her CEMT username. The chances of conflicts are very slim. After renaming users, make sure to sync all Open Dental databases.
Problem: 'Log in failed' message when trying to connect to an Open Dental database.
Solution: Sync the CEMT credentials for the user to the Open Dental database.
If the user provided a query, then the results will be aggregated into single result table. This would be analogous to a UNION.
Query by Connection:
The user would provide a query that returned one row. The result would show each connection in the first column, followed by the results in the other columns. In other words, the data would be broken down by connection. This would be analogous to a LEFT JOIN.
Reports: Additional aggregate reports will be added over time as requested.
Fee schedules could be transferred between any databases as well as sent to multiple databases simultaneously.
Settings such as
Definitions, Procedure Buttons, and Sheets could be transferred between databases.