Open Dental

Got it. Appreciate the fast response.

Hello again, I have an issue with the regular slots api: GET /appointments/Slots . We have blockouts where no appointment can be booked. However, the Slots API is not looking at this when returning the available slots. On the other hand, the Search in the OD interface is giving the right timeslots. ...

- It's happening with only couple of patients.
- For those patients, the other endpoints work.
- I'm able to call other enpoints with the current key

Hi team, The medicationpats is throwing an error on the get request. "Error. This is most likely a version issue. The version that the customer is using might be too old to support the API method used." Example URL https://api.opendental.com/api/v1/medicationpats/?PatNum=2 OD Version: 22.4.6

Hi Sarah, Setting both the OpsNumb and Provider number in the API is not working. As you can see in the pictures, for January 18th there is availability at 9am for the Restoration column. The Open Dental search, also is presenting that slot. However, the API only returns availability for 2pm on Janu...

Hi there, We have seen a mismatch between the /Slots API and what the Open Dental search returns in the software. The Slots documentation says: If a provider has existing appointments in multiple operatories, it considers all of them as a whole and only returns slots that are available in all operat...

Hi OD team.

Do you have any ETA for POST method for the InsPlan ?

Hello there, these features are super helpful. Is it possible to add a Post(create) InsPlan? I only see Get and Put.

Hi there, i have another question about planned appts. As you can see in the picture, this fake patient has multiple planned appts. The UI allows to reorder the appts. How can we extract the position from the API(or even a query) in this list? I cannot find any column indicating the position on the ...

The solution that worked was restarting the ApiService from the service manager.

Thanks to the team again.

Awesome. Thanks for the explanation; I could solve the issue.

I checked both databases and the name matches.

What other steps we can do to troubleshoot the issue?

I can also give you the machine IP and the credentials so you can test it. If you want it, please ping me in the internal chat or by email.

You are correct, the same body json is producing different outputs when using both endpoints. - Only one Open Dental Instance is running(double-checked that). - OD version is 22.3.21.0. EConnector version is the same(I found the version looking at the Properties in the EConnector.exe). The picture i...

Hi there, There is weird behavior while using the local api(https://www.opendental.com/site/apilocal.html) I'm creating an appointment using the api api/v1/appointments/ . The body of the POST request is { "PatNum": 2, "Op": 1, "AptDateTime": "2022-12-06 11:00:00", "AppointmentTypeNum": 1, "IsNewPat...

Hi there, I created a planned appt. Through the API, a new appointment was created for that planned appointment. Later, the user canceled the appointment. When trying to book the appointment again from the planned appointment, I'm receiving the following issues: Planned Appointment must contain at l...

Hi there, is it possible to have an ETA?

All that makes sense. If you could expose the NextAptNum on the API it would be awesome. Thanks so much.

Last question on this topic. After creating an appointment from a Planned appt with this procedure description "#2-BU, #3-O-C1(P)", the new appointment has a longer and more human-readable procedure description that is transformed to "Composite-1 Surf, Posterior, Build Up. " The question is, how do ...

How can we relate the Planned Appt with the New Scheduled Appt from the Appt ?

Is there any foreign key we can look at?

That makes sense, thanks for the answer and for updating the documentation.

Hi There, I have seen a new error on the API when I try to create a new patient with a First Name and Last Name that already exist in the database. The error is: A Patient with that information already exists in the database In the past, I never saw this error. Did something change on the database s...

Upgrading the beta version works for me. Thanks for the help.

We are having the same issue. Upgraded to new version 22.3.5 and API gives the same error.