For IT Administrators

2025 Compatibility Matrix

OraCore is architected to bridge the gap between fragmented legacy systems and modern cloud platforms. This page details our support for 25+ major systems across Dental, Orthodontic, OMS, and Medical-Dental environments.

Supported Ecosystems

OraCore integrates smoothly across the full range of dental and hybrid EHR environments—from solo private practices to enterprise multi-specialty health systems.

General Dentistry

Solo, Group & DSO

  • Open Dental
  • Dentrix (All)
  • Dentrix Ascend
  • Eaglesoft
  • Curve Hero
  • Denticon
  • CareStack
  • Easy Dental
  • Practice-Web
  • DentalMate
  • Adstra
  • Dovetail
  • AltaPoint
  • Genesis

Orthodontic

Cloud & Server Workflows

  • Cloud9 Ortho
  • Dolphin Mgmt
  • OrthoTrac
  • Genesis Dental
  • Gold Dental

Oral Surgery

Surgical & Referral Logic

  • WinOMS
  • Dolphin OMS
  • OMS Vision

Medical-Dental Hybrid

FQHCs, CHCs & Universities

  • AthenaOne
  • eClinicalWorks (eCW)
  • NextGen Office
  • NextGen Enterprise
  • ModMed

Legacy & Regional

Modernization without Migration

  • PracticeWorks
  • SoftDent
  • Mogo
  • Ace Dental
  • XLDent
  • DentiMax (All)
  • Viive

Enterprise Configs

Complex Architectures

  • Multi-database mirroring
  • Centralized data warehouses
  • Citrix / VDI environments
  • Hybrid Cloud + Local Imaging

Deployment Specifications

IT departments can use the information below to prepare environments for installation. We support secure, outbound-only communication protocols.

Cloud PMS Requirements

Ascend, Curve, Denticon, CareStack, AthenaOne, eCW, etc.

1. Connectivity

Standard web browser (Chrome/Edge) with secure HTTPS access.

2. Workstation Connector

Optional lightweight connector depending on API limits. Requires no local DB changes and uses encrypted session-level access.

3. Firewall

Standard outbound internet access on port 443 (HTTPS). No inbound port mapping required.

Server PMS Requirements

Dentrix, Open Dental, Eaglesoft, SoftDent, WinOMS, etc.

Server OS

  • Windows Server 2016 or later recommended
  • Local or network access to PMS database
  • Admin-level access required only during initial config

Security & Network

  • Outbound-only HTTPS (TLS 1.2+)
  • No inbound firewall exceptions needed
  • No database schema modifications

Database Types Supported

MySQL, MSSQL, c-tree, Firebird, and proprietary flat-files.
We operate via read-only extraction + API write-back.

Data Sync & Performance

Real-time Access: Appointments, treatment plans, providers, demographics, and clinical notes.

Zero Interruption: We do not inject code or operate as middleware. We use high-frequency polling with minimal resource usage.

Security Standards

  • Encryption: AES-256 at rest, TLS 1.2+ in transit.
  • Compliance: HIPAA-aligned infrastructure with full audit logging.
  • Isolation: Tenant-isolated data architecture.
  • Access: Role-based; no persistent elevated privileges.

System Specific Notes

  • Dentrix: G5.2+ Supported.
  • Open Dental: Supports replication & multi-clinic mode.
  • Eaglesoft: Version 18+ recommended.
  • Dolphin: Supports Imaging, Mgmt & OMS.
  • Hybrid/FQHC: Supports shared demographic bridges.

Common IT Questions

Does OraCore require DB access?
Yes, but only for read operations and specific write-back APIs. We strictly avoid direct schema changes to ensure PMS warranty validity.
Inbound firewall rules?
None. All communication is initiated outbound over secure HTTPS (Port 443).
Does OraCore modify clinical data?
No. OraCore writes new records (e.g., appointments) only when triggered by a user. It never alters existing clinical notes or history.
How are updates handled?
Cloud connectors are auto-updated. Server connectors update via a silent background service during off-hours.

Summary for IT Leadership

OraCore meets teams where they are—whether on a legacy server or a modern cloud EHR. We focus on low-friction deployment, secure data handling, and zero disruption to clinical operations.