API Event/Subscription - Tooth initial table support

[avie]

The table involving information about missing tooth etc is not yet supported by the API subscription/Database event system. Would you be able to add support for this ?

[DerekR]

I believe toothinitial is the table you are referring to. We do have a ToothInitials GET method that allows you to obtain the table rows filtered by PatNum.

[avie]

Yes indeed those items are accessible via the API. But my goal would be to implement a synchronization between my system and the open dental system. I already did something similar for patient info using the Database events system.

Thanks

[avie]

Up!

Thanks

[justine]

Up!

Thanks

Hello avie,

We can add the ability to subscribe to the toothinitial table via the API. However, this does not mean that any and every table can be, or will be, subscribable. (Some customers have 100's of clinics.) The API is not intended to keep a 1:1 sync of every customer's database.

In the meantime, I encourage you to use the ToothInitials GET endpoint.

Thanks!

[avie]

Than you for your reply.

I do understand your point and why going with the GET endpoint might be a better solution.

[avie]

Hi,
Thanks again for your response.
I am wondering how to edit and save tooth initial information via the Desktop App so that I can use the GET endpoint to retrieve this information.
At the moment I just get a 404 Not Found when trying to GET /toothinitials.
I tried to play with the ToothChart from the Desktop App by adding "Missing" teeth, drawings etc but it looks like nothing gets saved.

Thanks for your help.

[justine]

Hi,
Thanks again for your response.
I am wondering how to edit and save tooth initial information via the Desktop App so that I can use the GET endpoint to retrieve this information.
At the moment I just get a 404 Not Found when trying to GET /toothinitials.
I tried to play with the ToothChart from the Desktop App by adding "Missing" teeth, drawings etc but it looks like nothing gets saved.

Thanks for your help.

Hello avie,

What version are you on? ToothInitials GET was added in version 24.2.3.

Thanks!

[avie]

Hello,

I updated the Open Dental software and was able to fetch tooth initials data.

Would you know how to get the tooth nomenclature ? I read that it was related to the preferences but I could not find the "PrefName" associated with this config when calling the preferences GET endpoint. Or maybe there is a default value for this config ?


Thanks

[DerekR]

Hello,

I updated the Open Dental software and was able to fetch tooth initials data.

Would you know how to get the tooth nomenclature ? I read that it was related to the preferences but I could not find the "PrefName" associated with this config when calling the preferences GET endpoint. Or maybe there is a default value for this config ?


Thanks

Good morning Avie,

The PrefName associated with tooth nomenclature is "UseInternationalToothNumbers". The following is a summary of the ToothNumberingNomenclature enum:

0 - Universal (Common in the US, 1-32),
1 - FDI Notation (International, 11-48),
2 - Haderup (Danish),
3 - Palmer (Ortho.

You can also view the ToothNumberingNomenclature enum here: OpenDental Github

[JTS]

Up!

Thanks

Hello avie,

We can add the ability to subscribe to the toothinitial table via the API. However, this does not mean that any and every table can be, or will be, subscribable. (Some customers have 100's of clinics.) The API is not intended to keep a 1:1 sync of every customer's database.

In the meantime, I encourage you to use the ToothInitials GET endpoint.

Thanks!

We have completed this feature request. Subscriptions POST will now allow creating subscriptions to the ToothInitial database table, sending API Events to an endpoint of your choice when a row is added or modified.

This functionality is available as of version 24.4.30. Please see https://www.opendental.com/site/apievents.html and https://www.opendental.com/site/apisubscriptions.html for more information.