Page 1 of 1
**URGENT BENEFITS ISSUE**
Posted: Wed Feb 07, 2024 9:50 am
by omar22
Hello,
I have had MULTIPLE offices complain about percentages and frequencies being incorrectly uploaded in their Open Dental, and upon a quality check on my side, I've found it to be a glitch with Open Dental API. Is there any way to circumvent this issue?
Re: **URGENT BENEFITS ISSUE**
Posted: Wed Feb 07, 2024 11:55 am
by omar22
Also, the frequencies that used to populate fields in OD older versions
- Screenshot 2024-02-07 145427.png (105.77 KiB) Viewed 2610 times
no longer populate the fields in the newer updates of OD
- Screenshot 2024-02-07 125425.png (110.67 KiB) Viewed 2610 times
(see attached). How can I change the frequencies now to fill in to the correct fields?
Re: **URGENT BENEFITS ISSUE**
Posted: Wed Feb 07, 2024 1:35 pm
by justine
Good afternoon omar22,
Frequency Limitations implementation changed in v23.2 and now use CodeGroups.
23.1
23.2
23.3
To address this:
Enhancing the Benefits endpoints to include CodeGroupNum, is on the top of our development list.
Implementing CodeGroups GET is on the top of our development list.
I will reply to this thread as soon as they are complete.
Thanks!
Re: **URGENT BENEFITS ISSUE**
Posted: Thu Feb 08, 2024 6:32 am
by omar22
Is there a way to POST frequency in CodeGroups? I can't find any documentation on the API specification or anything to implement this new change.
Re: **URGENT BENEFITS ISSUE**
Posted: Thu Feb 08, 2024 8:42 am
by justine
omar22 wrote: ↑Thu Feb 08, 2024 6:32 am
Is there a way to POST frequency in CodeGroups? I can't find any documentation on the API specification or anything to implement this new change.
Unfortunately no, there is not. CodeGroups GET is currently in development. I have added CodeGroups PUT/POST to the API development list.
Thanks!
Re: **URGENT BENEFITS ISSUE**
Posted: Thu Feb 08, 2024 9:10 am
by omar22
great, thanks.
Re: **URGENT BENEFITS ISSUE**
Posted: Tue Feb 13, 2024 1:09 pm
by omar22
Can you also add a DELETE function? What would be the ETA on these?
Thank you
Re: **URGENT BENEFITS ISSUE**
Posted: Tue Feb 13, 2024 1:18 pm
by SLeon
omar22 wrote: ↑Tue Feb 13, 2024 1:09 pm
Can you also add a DELETE function? What would be the ETA on these?
Thank you
Benefits DELETE already exists and has been available since version 22.4.
The enhancement to Benefits to support CodeGroups just finished development today. You can expect it and the documentation to be released shortly in version 23.2.62 and 23.3.33.
Re: **URGENT BENEFITS ISSUE**
Posted: Tue Feb 13, 2024 3:11 pm
by justine
omar22 wrote: ↑Thu Feb 08, 2024 6:32 am
Is there a way to POST frequency in CodeGroups? I can't find any documentation on the API specification or anything to implement this new change.
Benefits were enhanced in version 23.2.62.
-GET no longer requires a PlanNum or PatPlanNum.
-GET now returns CodeGroupNum value.
-POST now supports creating a benefit utilizing a CodeGroupNum.
-PUT now returns CodeGroupNum value.
23.2.62 is expected to release later this week.
Thanks!
Re: **URGENT BENEFITS ISSUE**
Posted: Tue Feb 13, 2024 4:21 pm
by omar22
Great, thank you!
Re: **URGENT BENEFITS ISSUE**
Posted: Tue Feb 13, 2024 5:12 pm
by omar22
I tried using the POST /benefits with CodeGroupNum and it doesn't work (my demo versionis 23.3.32.0).
Please see payload:
{
"PlanNum": 74,
"CovCatNum": 0,
"Percent":-1,
"MonetaryAmt":-1,
"BenefitType":"Limitations",
"QuantityQualifier":"Months",
"Quantity":12,
"CodeGroupNum": 2,
"CoverageLevel": "None"
}
And this is how it looks in my OD:
- Screenshot 2024-02-13 201039.png (143.53 KiB) Viewed 2441 times
It just has a dash near category and doesn't work properly. Is there something wrong in my payload?
Re: **URGENT BENEFITS ISSUE**
Posted: Wed Feb 14, 2024 8:01 am
by justine
omar22 wrote: ↑Tue Feb 13, 2024 5:12 pm
I tried using the POST /benefits with CodeGroupNum and it doesn't work (my demo versionis 23.3.32.0).
Please see payload:
{
"PlanNum": 74,
"CovCatNum": 0,
"Percent":-1,
"MonetaryAmt":-1,
"BenefitType":"Limitations",
"QuantityQualifier":"Months",
"Quantity":12,
"CodeGroupNum": 2,
"CoverageLevel": "None"
}
And this is how it looks in my OD:
Screenshot 2024-02-13 201039.png
It just has a dash near category and doesn't work properly. Is there something wrong in my payload?
Good morning omar22,
The
benefit enhancements will be in the next release (
23.2.62 and
23.3.33), which should be next Thursday.
Thanks!
Re: **URGENT BENEFITS ISSUE**
Posted: Wed Feb 14, 2024 8:32 am
by omar22
justine wrote: ↑Tue Feb 13, 2024 3:11 pm
omar22 wrote: ↑Thu Feb 08, 2024 6:32 am
Is there a way to POST frequency in CodeGroups? I can't find any documentation on the API specification or anything to implement this new change.
Benefits were enhanced in version 23.2.62.
-GET no longer requires a PlanNum or PatPlanNum.
-GET now returns CodeGroupNum value.
-POST now supports creating a benefit utilizing a CodeGroupNum.
-PUT now returns CodeGroupNum value.
23.2.62 is expected to release later this week.
Thanks!
You initially told me later this week which I conveyed to my customers... is it now confirmed to be thursday of NEXT week??
Re: **URGENT BENEFITS ISSUE**
Posted: Wed Feb 14, 2024 8:35 am
by justine
omar22 wrote: ↑Wed Feb 14, 2024 8:32 am
justine wrote: ↑Tue Feb 13, 2024 3:11 pm
omar22 wrote: ↑Thu Feb 08, 2024 6:32 am
Is there a way to POST frequency in CodeGroups? I can't find any documentation on the API specification or anything to implement this new change.
Benefits were enhanced in version 23.2.62.
-GET no longer requires a PlanNum or PatPlanNum.
-GET now returns CodeGroupNum value.
-POST now supports creating a benefit utilizing a CodeGroupNum.
-PUT now returns CodeGroupNum value.
23.2.62 is expected to release later this week.
Thanks!
You initially told me later this week which I conveyed to my customers... is it now confirmed to be thursday of NEXT week??
Good morning omar22,
Next Thursday is tomorrow, which is later this week.
Thanks!
Re: **URGENT BENEFITS ISSUE**
Posted: Wed Feb 14, 2024 8:38 am
by omar22
Sorry I thought you meant 2/22. My apologies
Thank you for your quick and prompt responses.
Re: **URGENT BENEFITS ISSUE**
Posted: Fri Feb 16, 2024 7:25 am
by omar22
Hey sorry to bother you again, but it appears version 23.2.62 is still unavailable for my offices to update to. Do you have an ETA to when this version will be available?
Re: **URGENT BENEFITS ISSUE**
Posted: Fri Feb 16, 2024 9:38 am
by justine
omar22 wrote: ↑Fri Feb 16, 2024 7:25 am
Hey sorry to bother you again, but it appears version 23.2.62 is still unavailable for my offices to update to. Do you have an ETA to when this version will be available?
Good morning omar22,
23.2.62 has been released.
Thanks!
Re: **URGENT BENEFITS ISSUE**
Posted: Fri Feb 16, 2024 1:32 pm
by omar22
Awesome thanks! CodeGroups will always be the same across all clinics, unlike covcats, right? for example FMX/PANO will always be CodeGroupNum 2, right?
Re: **URGENT BENEFITS ISSUE**
Posted: Fri Feb 16, 2024 1:52 pm
by justine
omar22 wrote: ↑Fri Feb 16, 2024 1:32 pm
Awesome thanks! CodeGroups will always be the same across all clinics, unlike covcats, right? for example FMX/PANO will always be CodeGroupNum 2, right?
Good afternoon omar22,
CodeGroups (Frequency Limitations) can be configured however the practice wants. So, while it may be likely that CodeGroupNum 2 is FMX/PANO, it is not guaranteed.
CodeGroups GET documentation should be released shortly.
Thanks!