Setting the Record Straight on Interoperability and Customer Choice

/in /by

Dentrix and Henry Schein One attempt to frame their latest platform changes as purely security-driven. While we agree that protecting patient data and system integrity is critical, we believe it’s equally important to provide clarity around interoperability, customer choice, and the full context behind these decisions.

Our Commitment to Open Partnerships

At Vyne Dental, interoperability is not just a talking point—it’s something we actively invest in.

We maintain active integration partnerships with both Open Dental and Patterson (Eaglesoft), where we pay fees to support the development and maintenance of APIs that enable reliable data exchange.

These partnerships demonstrate a simple truth: when APIs provide the right data and functionality, we support and participate in those ecosystems.

Our approach has always been to meet practices where they are—supporting flexible integration methods that allow providers to choose the workflows that best serve their patients and businesses.

Our Efforts to Engage with the Dentrix API Exchange

We have made efforts to engage with Henry Schein One’s developer program and API ecosystem since March 2025. The reality is more complex than it’s been portrayed. The Dentrix API Exchange does not currently provide the data required for claims submission workflows. Additionally, participation in the program would require us to abandon existing integration methods that thousands of practices rely on today.

In other words, joining the Dentrix API Exchange as it stands today would not preserve customer choice—it would limit it.

We have expressed willingness to invest financially to support the development of necessary APIs, reinforcing that our goal is collaboration—not circumvention.

The Bigger Picture: Choice and Access

Dental practices depend on the ability to choose the partners and workflows that work best for them. While Dentrix positions its API Exchange as the “intended path” for interoperability, the current limitations of that ecosystem create real barriers for providers who rely on established solutions.

This is not simply a technical debate—it’s about ensuring that:

  • Practices retain control over how their data is used
  • Providers are not forced into a single workflow or vendor ecosystem
  • Innovation is not restricted by a single vendor, or incomplete or constrained integration options

Moving Forward

We remain committed to working constructively with all partners in the dental ecosystem—including Henry Schein One—to advance secure, effective interoperability.

But true interoperability requires more than a single access point. It requires complete, functional APIs and a commitment to enabling, not restricting, customer choice. This approach is already reflected in our established integrations with Open Dental and Patterson (Eaglesoft), where complete, functional APIs support reliable, real-world workflows at scale.

We will continue advocating for the providers we serve and supporting the integrations they depend on every day.