ODBC Solutions to Access Data at Any Time
The AdvancedMD open database connectivity (ODBC) interface provides direct read-only access to your data at any time. Choose from a dedicated or shared environment to manage your data.
AdvancedMD Open API Architecture & ODBC Server Overview
Our open API architecture lets you build your own reporting platform, generate custom data feeds for business partners, and countless other purposes. Most database tables in AdvancedMD are available via ODBC, including patient demographic data, appointments, and financial transactions. Most clinical data is also available from our EHR.
AdvancedMD’s open database connectivity is provided by an ODBC server, which is responsible for managing ODBC connections, authentication, and authorization, and transferring the data. This server is separate and distinct from your database server (whether you have a dedicated database server or share a server with other clients). Your ODBC server can be dedicated or shared, depending on your needs.
24/7 Access with ODBC Access Kit
You can access your AdvancedMD data at any time with our secure cloud ODBC access kit. The kit provides:
- ODBC read access to your live AdvancedMD office keys
- Local Windows-based ODBC driver to be installed on your workstation or laptop
- Data dictionary describing all tables, fields, and key relationships
- Ready-to-use scripts for creating, populating, and syncing a local data copy
Simple Report Creation
There’s a simple method that lets you run reports and query the system directly. Connect your own report-writing software directly to AdvancedMD using the ODBC driver as the database connector and write reports against your live data. Because this is an ODBC connection and not native Microsoft SQL, there are query limitations which would generally restrict this type of usage to simpler reports.
Create a Data Warehouse
AdvancedMD provides a ready-to-use SQL script to create your own Microsoft SQL database with copies of your own data. You can update at any interval you wish. Once your data warehouse is up and running you can use just about any reporting, query, or analytics tool to extract and report on your data. You may use any database, but the ready-to-use scripts are for MS SQL.
Shared ODBC Server Uses & Scenarios
- Regularly scheduled, after-hours download of changed and new data (“deltas”) into your own data warehouse
- Light to moderate real-time reporting
- Non-mission-critical access to data for interfacing with other systems
- Prompt platform support and maintenance window notification aren’t critical
- Small to moderately sized office keys (up to 500 patient encounters per day)
- Up to ten office keys in a CBO
NOTE: All client data is stored privately and is not shared.
Dedicated ODBC Server Uses & Scenarios
- Heavy real-time reporting (more than 100 reports during business hours per day)
- Mission critical applications (where an hour of downtime would negatively impact your business)
- 24×7 telephone platform support and advanced notification of maintenance windows are needed
- Large and extremely large office keys (over 500 patient encounters per day)
- More than ten offices in a CBO
- Any other application where large queries must be run frequently during your business day
Scenerios
| Shared | Dedicated | |
|---|---|---|
| Populate and update local data warehouse | ||
| Light to moderate real-time reporting | ||
| Small to moderate-sized office keys | ||
| Up to 10 office keys in a CBO | ||
| Heavy real-time reporting during business day | – | |
| Mission-critical applications | – | |
| Large office keys | – | |
| More than 10 office keys in a CBO | – | |
| Partners who use ODBC to provide services to AdvancedMD clients |
– |
Uptime & Support
| Target uptime | 99.9% | 99.99% |
| Platform support* availability | 6am-6pm MT | 24×7 |
| Platform support* methods | Service Desk (Email) | Service Desk (Email) Phone |
| Maintenance window notification method | Status Page | |
| Maintenance window notification timeline | 1-3 Days | 1-2 Weeks |
* “Platform Support” is provided in the event that ODBC becomes unavailable or is performing poorly. Our support technicians will help identify any problems with your local ODBC driver or, if there is an issue with your ODBC server, they will work with our Operations team to diagnose and remediate the problem. “Developer Support” is still currently provided via the Interops Service Desk. Additional Developer Support options will be available in the future.
