Open Dental Forum

Per Jordan Sparks, they are deprecating plugins, but the plugins functionality will not be turned off yet.

Open Dental whitelisted most of the existing Vendors plugins like Mopensoft, Flex, PatientXpress, Yapi, Modento, Card connect, DentalXchange, Moolah, X-charge, PaySimple, PayConnect
etc......

Using the API no doubt offer better security, less maintenance, because with the plugin option, if OD changes something, it can break the plugin unintentionally.
For Developers planning though, questions to Open Dental:
1- When does Open Dental anticipate plugins to be deprecated?
2- or support for plugins , will it get removed ?
3- end of year? Just for the Developers to stay ahead of the curve.

API Specification available here
https://www.opendental.com/site/apispecification.html

It's a gradual process that requires constant feedback and adjustment. So it really is impossible to say. The current plan is to start with subtle warnings that don't actually interfere with functionality. The other part of this is that we don't want people to be afraid to update versions of Open Dental. So the warnings have to be completely disconnected from which version you are on.

According to OD, their plan, If you want to write to OD database in the future, you have to use the API, other methods will not be allowed.

Does not matter how you read it, or what approach you have, or work in parallel, what matters is when you want to write the data, you will have no choice, but to use the API
All vendors are whitelisted now and no dental office need to panic, but it is a lot of work for developers, they need to be ready.

In addition, OD is planning on charging the developer and the dental office for reading and writing this data.

The econnector will be running, the Developer will have their own API key, and the dental office will have their own API key, and you need both keys to access your own data and pay for it.

Developers need to contact OD and get their own API key and start working.
OD offer special links for a developer to test their addons with their API, at no additional charges.


=========================================================================================

jordansparks wrote: Fri Sep 17, 2021 10:25 am It has come to my attention that there are some plugins that are extensively writing to the database. This abuse needs to end. It's dangerous and unstable. We've clearly stated on the plugin page from day one that plugins should never write to the existing database tables. The API is the only approved method for writing to the database. We will be putting new measures in place designed specifically to block plugins from making changes to the database.

===========================================================================================

jordansparks wrote: Sun Nov 07, 2021 7:14 am Plug-ins must now be whitelisted in order to work.
https://www.opendental.com/site/pluginwhitelisting.html

If you have been using a plugin/addon for a while, probably your plugin is whitelisted, the functionality is not interrupted, and the dental office should not panic, you will be OK
===========================================================================================


Note:
I am not an employee or affiliated with Open Dental or any other developer or vendor company. Just a happy Open Dental user since 2010, and looking for answers.

>In addition, OD is planning on charging the developer and the dental office for reading and writing this data.
Not quite. No charge to anyone for reading. If writing, there will be a very small charge to the developer, not to the dental office.

Jordan. Thank you for the clarification.

Hi Dr. Sparks

I am looking to place a button in images module, that will initiate communication with dentists, and the rest of communication will happen via REST. Will you guys still accept code contributions for plugins still? I understand the plugin workflow is being deprecated, so that is why I am asking whether you guys will accept still 3rd party contributions to your code base (to accomplish the task of add a button to images module)

Have you considered setting a program link that point to an executable

We continue to deprecate plug-ins. A program link button sounds like a perfect fit.