Central Enterprise Management Tool ( CEMT )
See Advanced Topics.
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.
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.
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 Central Manager - Admin CEMT window will open.
From this central location you can easily:
Below are descriptions of the options on the Central Manager window.
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).
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.
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.
Query Aggregation: 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: Fee schedules could be transferred between any databases as well as sent to multiple databases simultaneously.
Settings: Settings such as Definitions, Procedure Buttons, and Sheets could be transferred between databases.