Open Dental

saskia

Wondering roughly where in the development queue this feature is? Thanks!

saskia

Good afternoon! Thanks for the quick response - good to know which field I'm looking at but struggling to understand how the values work. I think "Pattern": "//XXXX//" Means 2 x 5 minutes assist time, followed by 4 x 5 minutes doctor time followed by 2 x 5 minutes assist time? For a total of 40 minu...

saskia

I'm looking at the appointment API (https://www.opendental.com/site/apiappointments.html) and was hoping to be able to see how long an appointment is. Am I overlooking something or can I make a feature request? Thanks!

saskia

A client added in the API key, but when I go into my portal, the name and version doesn't match. The key is correct so I'm scratching my head as to what is happening and whether I should be concerned. The practice name on my portal shows as Relaxation Dental and the version as 23.1.36.0. The client ...

saskia

Thanks, good to know that unassigned keys are not charged! I might be able to work with something there.

saskia

Let me know if I'm overlooking this somewhere, but I would love to be able to generate new keys via the API so I can simplify the process of onboarding my clients.

saskia

Gotcha - so in 23.3 we can set prePayment to false and everything will flow through as expected. Thanks!

Any rumors as to when 23.3 may come out of beta?

saskia

That feels really clunky - so there's no way for us to make sure when we're posting from the API to make sure it actually hits the ledger like we'd expect without our client doing something on their end? If I understand correctly, they have to create a definition with specific settings and then sele...

saskia

There have been a number of changes around payment plans and reading the documentation I can't figure out what we're doing wrong when posting payments to payment plans. We can see the payment on the plan but on the ledger it shows up under 'hidden splits' and the actual amount due on the plan doesn'...

saskia

We take care of the statements, we just want to be able to let OpenDental know that a statement was made/sent. THanks!

saskia

We're signed up to a subscription, but when we set a workstation, we are no longer getting anything. We made sure we had the right workstation name (there's only one option in our test environment so nice and easy here) [ { "ComputerNum": 1, "CompName": "LAPTOP-9OO9FOOR", "LastHeartBeat": "2024-01-1...

saskia

Are these created in OD or via the AP: Procedures were created in OD, we pulled in the values using the procedure log API Are these Completed procedures?: I'm not entirely sure for the production example, but the test that I ran on my demo instance are all completed and reproduces the same issue Ho...

saskia

I'm looking for the ability to post to the ledger that a statement has been sent - am I overlooking this in the documentation or is this a feature request?

Thanks!

saskia

Our clients have a common scenario where the pricing on the procedure for what the patient owes is incorrect. This mean when we send the request to create the dynamic plan for the lower (correct) amount, the values we're saying to create the plan for are entirely ignored. How should we address this ...

saskia

Thanks! Once added, will we be able to post data to those created patfielddefs or is that a separate request?

saskia

Any chance someone can point me in the right direction of API documentation on patient field defs? I'm looking at creating them via API and then populating data. Is this possible? I couldn't see anything under definitions, is it somewhere else or not supported in the API? Thanks.

saskia

Hey! I can't reproduce it in our test environment either - the only thing I was able to reproduce was sending payType to an OD instance that didn't support payType, and the response I received still showed the payType I had configured rather than the default - so the response is misleading as it's n...

saskia

Troubleshooting an issue whereby we're sending the payType, however, in OpenDental the payType ends up being the API default rather than what was sent. Things we've checked: Client is using a version that supports this feature (they're on 23.1.43/45/46 - they have multiple locations) payType exists ...

saskia

I think I understand - I'll have to take a look at my demo instance to wrap my head around how the charges/payments link to one another. The big challenge we have is getting all the patients that have an outstanding balance, and then getting all the outstanding charges for those patients (again wher...

saskia

We've been using the statement file to generate a statement for the patient as it's the easiest way to get the appropriate list of procedures out of OpenDental (it shows everything since a zero or negative balance which is what we're looking for). Then when patients pay (often using a payment plan) ...

saskia

One of big use cases we have is for AR invoices generated using the statement XML file - Is it possible to add the procNums to this file? Then when patients pay their invoice, we know which procedures to associate the plan to.

saskia

They're making these plans in our product, not directly in OpenDental. Within our product, users can select the patient, the payment amount and then head straight to paying. That's a lot less clicks than selecting patient, then selecting the procedures, then going to pay. This one we can certainly g...

saskia

Couple of different scenarios - sometimes it's purely for speed - they want to get the payment setup quickly and get the patient out the door, deal with the splits later (or, as OpenDental for straight up payments just applies to the oldest first, that meets their requirements so they can keep it su...

saskia

Awesome! Thank you. To make sure I understand how we'd use this - we would call the GET PayPlanCharges to see which ones are due and which ones are not. And then we'd POST payments towards a specific PayPlanCharge (if I understand correctly, a PayPlanCharge is basically an installment right?), addin...

saskia

Any update here? We'd like to post payments correctly to these plans but it's a real lucky dip right now and if folks have other outstanding items payments end up on the wrong procedures every time as the PP charge will always be the most recent one, even if the underlying procedures are far older. ...

saskia

This seems like a big loss - we have clients who want to be able to create payment plans without needing to associate it with specific procedures. Will dynamic payment plans support this in the future?

saskia

Gotcha - so as long as we don't care that it may take a few minutes, we can just send a large amount of requests, and they'll simply be addressed in due course? Clients could be sending out emails for all patients who have a balance, which can often be 200+, but no one is concerned if it takes a few...

saskia

We're seeing requests timeout and have been assuming that's OD throttling us - is this not the case? From what I can see in the documentation, it's 1 request per second - what happens when we go over that? We want to make sure the data we're trying to write back gets written back and we don't have t...

saskia

I feared that was the case. We'll have to build in our own delay to ensure we don't get throttled when we're trying to post hundreds of comm logs when we do a batch send. A real bummer, this is definitely an API where being able to bulk update would be very useful and reduce load for both sides.

saskia

Hey folks - wondering if it's possible to do a bulk update on the comm logs? (https://www.opendental.com/site/apicommlogs.html) At times we send out hundreds of messages on behalf of our client and looking to write those back, but we'd quickly be hitting out throttle limit (1 request per second if m...

saskia

Thanks for the update! Any rough idea of when my request might make it through your development lifecycle? We'll need to do some work on our side of course and doing some rough resource planning. Thanks!

saskia

Hey - checking in to see where in the pipeline these requests might be? I've got some related enhancement requests around the regular patient payment plans that were submitted around the same time - I suspect they may have all been lumped together? Thanks!

saskia

Checking this made it on the list? If so, any chance of a rough ETA? Thanks.

saskia

Would it be possible to add this as a feature request? We're really just after the data that's in the Billing file that can be generated from OpenDental directly.

Thanks!

saskia

THanks!

Then I'd love to add another feature request where we can specify payPlanNum and set isPrePayment to false to ensure the payment is allocated to the payment plan as opposed to other procedure(s) first.

saskia

Could we add that to the feature request list? The ability for a payment to be associated with a payPlan, regardless of whether there are older charges or not? And what is the rough ETA of the PayPlanCharges GET update that mentioned? Lastly - I'm still struggling to get payments associated with the...

saskia

Gotcha - so we'd call this first, and based on the response, either post with the payPlanNum and isPrePayment set to true, or exclude the payPlanNum as well as isPrePayment? Have I understood correctly? What about the issue I'm seeing now where if we post a payment, it won't go to the plan if there ...

saskia

We tried that as well, but the payment is then being associated with the oldest charge, which isn't necessarily the one associated with the plan. I was hoping for this to be a little simpler where we supply the payPlanNum to ensure the payment is associated with the plan, and have OpenDental decide ...

saskia

We're posting payments according to the Payments POST documentation for dynamic plans: including the payPlanNum and setting isPrepayment to true. The result in OpenDental puts the payments under 'Hidden Splits' and doesn't decrease the 'amount due'. What should we be doing to get these payments to c...

saskia

Thanks! We're only looking for the aging balance and from what I can see, the GET ServiceDateView gives us absolutely everything, not just what is due (ie 'all transactions since zero or negative balance' from the Billing section in OD). Basically we're looking for far less data than GET ServiceDate...

saskia

We're looking to pull the aging balance along with the detailed breakdown of what goes into the balance in order to send statements to all patients that have an open balance over 30, 60 or 90 days. Ideally we'd like to simply request this data for all patients with an open balance, but I don't think...

saskia

Thanks!

saskia

Two enhancement requests: Is it possible for PayPlans POST to gives us a JSON response instead of text? We've done some work with PayPlans POST Dynamic already which gives us JSON responses and would love for these two to be the same. Is it possible to have the PayPlans POST response include the pay...

saskia

Awesome! Thank you! Do you know how long it typically takes for versions to go from beta to full release? I know I'm going to have clients who don't want to run a beta version so if there's any ballpark I can give them that would be great. Thanks!

saskia

Is there a target release date for this? Thanks!

saskia

Is there a target release date for this yet? Thanks.

saskia

I'm wondering if there's an update on this one? Thanks!

saskia

I'm wondering if there's any update on this? Thanks!

saskia

We've got dynamic payment plans working pretty well via the API but we are struggling with prepayments. I'm sure it's a setting we're missing somewhere, but when a patient does a prepayment and we post this, it sits as a prepayment rather than being associated with the payment plan. Originally we th...

saskia

SLeon wrote: ↑
Tue Apr 11, 2023 11:24 am
I have added this Payment Type feature to our development list and we will start on it soon. I will update this thread with our progress.

Awesome! Our clients are going to be very excited about this. Appreciate you hearing us out and adding this to your feature list.

saskia

This is what I'm hearing from my clients. They want more granularity in what we're posting - it makes sense that yes, it's all API, however, they want to know more than just 'came from API'. Because we offer more than just one payType, they want to see that reflected when we post back. It's the leve...

saskia

Sadly that really doesn't help us - we're the ones that need to dictate what the pay type is, and it will vary (ie sometimes it's cash payment, sometimes a check, etc.) and thus depending on what the payment it, we'd like to post with the right payType, rather than whatever the API is set to. It'd b...

saskia

When POSTing a payment we'd like to be able to set the payType based on how the patient has actually paid. We figured out we can create/GET payTypes via definitions but then realized we can't actually use any payTypes we've created when posting various payments.

Search found 53 matches