Open Dental

Hey everyone,

tl;dr How can I enable the FHIR API with the trial version.

I am new to Open Dental development and am interested in connecting with the API. I downloaded the trial version to play with the API but it looks like I need to have an eServices account. I have hit the test api with postman and Java with success and was hoping to repeat that with the trial version. Is it possible to enable FHIR in the trial version? Or is my best bet to learn more about the middle tier?

Thanks,
plebet

As you have found, a valid registration key is needed to setup a FHIR API. We can possibly give you a developer registration key. I'll PM to get that rolling.

Thanks Chris,

I appreciate the help!

I am having this issue as well - can you please provide a developer registration key?

I'll send you a private message, Daniel.

I am trying to enable FHIR with trial version,

Please provide the Registration Key for developer.

I appreciate your help regarding registration key.

Thanks.

I'll send you a private message as well.

Thanks a ton Chris

Hi Team,

I am trying to consume FHIR APIs with trial version and developer registration key, What I observed is the data in demo database and the response of the APIs does not match. Please let me know if I am doing something wrong.

Also I would like to know about certain details as mentioned below:

1. Is there any API endpoint which provides patient's treatment plan containing procedures codes(CDTs)?
2. Is there any API endpoint which provides patient's insurance details such as subscriber_id, insurance provider etc.

Please let me know if it is possible with either in paid version/trial version or not.

Thanks in advance

dhiraj wrote:1. Is there any API endpoint which provides patient's treatment plan containing procedures codes(CDTs)?

There is not, although one of my coworkers just started writing the code for this.

dhiraj wrote:2. Is there any API endpoint which provides patient's insurance details such as subscriber_id, insurance provider etc.

No, this is not available.

Thanks for the update chris

Chris -

I am trying to enable FHIR with trial version,

Please provide the Registration Key for developer.

Thanks
Santosh Jami

Yes, I will get you a registration key.

However, starting in version 18.4, it will no longer be possible to enable FHIR with a trial version. You will need the full version of Open Dental to use FHIR. Now if you have a developer registration key, you can download the full version and set up FHIR.

Hello,

I'd like to also have a developer's registration key to setup FHIR. Right now when I do Menu Setup -> Advanced Setup -> FHIR then I get the error `No eService account found for this registration key`.

I have the OpenDental trial version 18.3.50.0 which is the one shown when I do Help -> About. I'm not sure whether this is the version for trial Client or Server or both?

Many TIA,
Best regards,
Giovanni

Giovanni,

Go ahead and email vendor.relations@opendental.com to request a developer registration key.

Is there a time limit on using any given developer key and can you please provide me the instructions on incorporating updated CDT codes once the key is inputted?

There is no time limit for developer keys. It should work indefinitely. To update to the newest CDT codes, you can run the "D Codes" tool: https://opendental.com/manual/procedurecodetools.html.

Thanks Chris for letting me know about the key duration and the direction on the codes. I am a bit wary by the statement, "this option does NOT work in the compiled version" ??

One of the only differences between the compiled version and the version we distribute is that the version we distribute includes CDT codes in one of the dlls. If you have a developer key, you can download the version that we distribute and therefore obtain the newest CDT codes.

Ok, I understand the difference now. Is the current distribution v. 19.2?

Yes, 19.2. The beta version 19.3 is also available for download.

Hi,
We're evaluating the FHIR. Can you please share the developer registration key for v19.1

Thank you!

If you would like to use our test environment, you can find the developer key in https://www.opendental.com/resources/Op ... -4Spec.pdf. Our test environment is currently on version 19.4.

If you would like to connect to your own database, we will need to issue you a developer API key. You can request one from vendor.relations@opendental.com. In your email include:

Developer name:
Company name:
Email address:
A list of the API Resources you need access to, the level of access such as read/write/update:
A description of the application you are intending to build (type and purpose):

cmcgehee wrote: ↑

Mon Nov 04, 2019 4:50 pm

There is no time limit for developer keys. It should work indefinitely. To update to the newest CDT codes, you can run the "D Codes" tool: https://opendental.com/manual/procedurecodetools.html.

Even after inputting my developer key, the D codes tools as well as the others are grayed out with the exception of N tools. Is there another step I need to perform?

To use the D codes tool, you need to enter a valid registration key (this is different from a developer API key). You can email vendor relations if they have not given you one.

Thanks for the clarification... I got confused by your previous statement "If you have a developer key, you can download the version that we distribute and therefore obtain the newest CDT codes."

Is the registration key needed in addition/on top of the developer key...How long would this process take?

I admit it can be a little confusing how we have developer registration keys, developer API keys, and customer API keys. I'm going to try to start referring to developer registration keys as testing registration keys.

If you want to download the CDT codes, you will need a testing registration key in addition to a developer API key. Sometimes when we give an individual a developer API key, they are working with an existing office so they don't the testing registration key.

Yes it is... why these multiple layers of keys... Isn't OD open source at the software's core; it would then seem close-sourced and proprietary due to these loops/tiers we have to jump through haha.

Would it be faster to get a "testing registration key" if I call OD's developer line directly or just email the vendor one?

The main reason we need to issue a testing registration key is because the CDT codes are proprietary. We have to pay a royalty for each registration key we give out. Open Dental as the company follows an open core model (https://en.wikipedia.org/wiki/Open-core_model) where the main software is free and open source, and additional features are proprietary.

It would be faster to email vendor relations. OD developers don't have a direct phone line.

Oh ok, I understand. Thanks for explaining and providing the link for further reading on the open model.

I did email them yesterday but still haven't heard back...

Hi,
Can we get Patient auto chart and treatment plan data through API?
Thanks,
Poonam

We just release chart module data, and we could make a method for TP data, if that's what you are asking for. Maybe start a new thread instead of reusing the very old and unrelated thread.

I am also trying to enable the API with the trial version. Can I receive a key?

mcardosog wrote: ↑

Wed Apr 05, 2023 10:10 pm

I am also trying to enable the API with the trial version. Can I receive a key?

The trial version of Open Dental is not intended for API testing, we have a public demo specifically for this.

Please check out the Getting Started guide and API documentation.