Open Dental Forum

beacondental wrote: Thu Feb 27, 2025 3:45 am Thanks for the previous help.

One more question I have is, how can I find the Pri Ins Amount shown in the treatment plans module for an active treatment plan?

If you can help me with the query or the API, it will be very helpful.

Thanks in advance.

SLeon wrote: Mon Feb 10, 2025 8:51 am Good morning,

You are attempting to use a procedure with an incorrect status. From our schema:

PrecedureLog.ProcStatus.png


As the error message indicates, you cannot use procedures that are of type TP.

beacondental wrote: Wed Mar 05, 2025 9:22 pm

SLeon wrote: Mon Feb 10, 2025 8:51 am Good morning,

You are attempting to use a procedure with an incorrect status. From our schema:

PrecedureLog.ProcStatus.png


As the error message indicates, you cannot use procedures that are of type TP.

I am already checking the ProcStatus=1 in my query. Still, I see this error.

Also, the ProcNum from the example I shared in the beginning of this thread is part of an Active Treatment Plan only, then why the error?

beacondental wrote: Tue Apr 08, 2025 9:23 pm Hello,
I selected procedures from the Active Treatment Plan and attempted to create a Pre-Auth claim, but encountered the same error:
"Cannot create a PreAuth claim with procedures from a saved treatment plan."
I’ve attached the relevant screenshots.
Could you please guide us on this matter? This issue has been ongoing for quite some time and is currently stalling our development efforts.
""

https://api.opendental.com/api/v1/proctps?TreatPlanNum=65212

obv123 wrote: Fri Sep 12, 2025 3:14 pm Hello OD team,

I am experiencing the same issue as beacondental. I have read and understood the conversation so far. My additional question is:

In the OpenDental UI it is possible to save and sign a TP and then create a PreAuth for the same procedures by selecting them from the "active" treatment plan. Is there any way to do an equivalent thing through the API?

Best,
Alex

obv123 wrote: Tue Sep 16, 2025 3:19 pm Hi RyanH,

Thank you for the response. Your suggestion makes sense. Unfortunately, it's our process to have the patient sign the treatment plan before they leave the appointment where the services were planned. The prior auth claim gets created later after review from our billing team (which is part of what we're trying to automate).

Is there any way I could request a modification to the post claims endpoint to support this?

Thank you,
Alex

obv123 wrote: Tue Sep 16, 2025 3:19 pm Hi RyanH,

Thank you for the response. Your suggestion makes sense. Unfortunately, it's our process to have the patient sign the treatment plan before they leave the appointment where the services were planned. The prior auth claim gets created later after review from our billing team (which is part of what we're trying to automate).

Is there any way I could request a modification to the post claims endpoint to support this?

Thank you,
Alex

beacondental wrote: Wed Jan 28, 2026 10:13 pm Hi Team,
For Claims POST API, the example response is :
Example Response:
{
"ClaimNum": 35879
"PatNum": 1337,
"DateService": "0001-01-01",
"DateSent": "2023-05-21",
"ClaimStatus": "W",
"DateReceived": "0001-01-01",
"PlanNum": 31,
"ProvTreat": 8,
"ClaimFee": 295.5,
"InsPayEst": 220.0,
"InsPayAmt": 0.0,
"DedApplied": 0.0,
"IsProsthesis": "N",
"PriorDate": "0001-01-01",
"ReasonUnderPaid": "",
"ClaimNote": "",
"ClaimType": "PreAuth",
"ProvBill": 2,
"PlaceService": "Office",
"AccidentRelated": "",
"AccidentDate": "0001-01-01",
"AccidentST": "",
"IsOrtho": "false",
"OrthoRemainM": 0,
"OrthoDate": "0001-01-01",
"PatRelat": "Self",
"PlanNum2": 28,
"PatRelat2": "Spouse",
"WriteOff": 0.0,
"ClaimForm": "19",
"InsSubNum": 894,
"InsSubNum2": 856,
"PriorAuthorizationNumber": "",
"MedType": "Dental",
"CustomTracking": 0,
"customTracking": "",
"CorrectionType": "Original",
"ClaimIdentifier": "1337/35879",
"OrigRefNum": "",
"OrthoTotalM": 0,
"ShareOfCost": 0.0,
"SecDateTEdit": "2023-05-21 10:25:44"
}

Can you please update SecDateTEdit to follow the standard protocol, i.e.,"SecDateTEdit": "2023-05-21T10:25:44" instead of "2023-05-21 10:25:44"?
The current format causes issues when mapping data using standard libraries.