Need API to effectively allow us edit procedures which recreates related tables data as required

[avdhutkotkar]

Context :
1. We are editing a procedure on a claim
2. OD doesn't let us do that in some scenarios (e.g. treatment area is different)
3. So we delete the claim and recreate it
4. When we do this claim notes and other things get orphaned and need to be attached to the new claim
5. We don't know all possible data types we'd need to reassign and there is probably not an API call for each of them
6. We'd love for OD to give us a way to just request an edit to a procedure and have OD do the deletion and recreation with related tables data for us if it's a required step.
7. But if not, can we have an API call that allows us to reassign all orphaned records from an old claim to a new one?

Current case that we faced this issue (again there could be more such cases that we haven't encountered yet):
We created Status note for the OLD claim and while trying to update the procedure, due to some restrictions when recreated claim the status note stayed orphan (linked to deleted claim) and we don't have a way to update the ClaimNum to that existing claimtracking entry. as there is no update support for claimNum.

PUT /claimtrackings/{claimTrackingNum}

[RyanH]

Context :
1. We are editing a procedure on a claim
2. OD doesn't let us do that in some scenarios (e.g. treatment area is different)
3. So we delete the claim and recreate it
4. When we do this claim notes and other things get orphaned and need to be attached to the new claim
5. We don't know all possible data types we'd need to reassign and there is probably not an API call for each of them
6. We'd love for OD to give us a way to just request an edit to a procedure and have OD do the deletion and recreation with related tables data for us if it's a required step.
7. But if not, can we have an API call that allows us to reassign all orphaned records from an old claim to a new one?

Current case that we faced this issue (again there could be more such cases that we haven't encountered yet):
We created Status note for the OLD claim and while trying to update the procedure, due to some restrictions when recreated claim the status note stayed orphan (linked to deleted claim) and we don't have a way to update the ClaimNum to that existing claimtracking entry. as there is no update support for claimNum.

PUT /claimtrackings/{claimTrackingNum}

Hello avdhutkotkar,

The API enforces a claim to be in the correct state before allowing deletion. During deletion of a claim, the API mirrors how Open Dental deletes a claim in the UI. In Open Dental, if you delete a claim, any associated claimtrackings will still exist in the database, orphaned. The API does not implement features that Open Dental doesn’t offer.

Thanks!

[avdhutkotkar]

Hello,
Thanks for the reply.
For the custom tracking case,
We will have to recreate the claim note again with the information we have from old claim.
Otherwise, For our application this case will cause problem in the Aging claim with display of claim's note in Open Dental.

Current API supported parameter.
Example Request:
POST /claimtrackings
{
"ClaimNum": 15,
"Note": "Missing attachment.",
"TrackingDefNum": 339,
"TrackingErrorDefNum": 340
}
Can we have optional parameter for the DateTimeEntry to use it in Post , so we can create the note in the past date ?
Which will mirror the behaviour we need to move the note from old claim to new claim.

OR
Have support to update the existing Claim tracking entry for ClaimNum
PUT /claimtrackings
(This was initially present in the request, which was mentioned as won't be happening)

Please suggest a solution to solve this problem to move the existing note to the new claim, using open dental API.

[justine]

Hello,
Thanks for the reply.
For the custom tracking case,
We will have to recreate the claim note again with the information we have from old claim.
Otherwise, For our application this case will cause problem in the Aging claim with display of claim's note in Open Dental.

Current API supported parameter.
Example Request:
POST /claimtrackings
{
"ClaimNum": 15,
"Note": "Missing attachment.",
"TrackingDefNum": 339,
"TrackingErrorDefNum": 340
}
Can we have optional parameter for the DateTimeEntry to use it in Post , so we can create the note in the past date ?
Which will mirror the behaviour we need to move the note from old claim to new claim.

OR
Have support to update the existing Claim tracking entry for ClaimNum
PUT /claimtrackings
(This was initially present in the request, which was mentioned as won't be happening)

Please suggest a solution to solve this problem to move the existing note to the new claim, using open dental API.

Hello avdhutkotkar,

A question like this requires more detail than we can effectively cover here. In the Developer Portal there is a email address specifically for API related technical and implementation questions. Please reach out there, as that will be the fastest way to get this resolved.

Thanks!