We would like to request that a new API be created to enable us to split a claim the way the application does when a user clicks Split Claim in the Edit Claim window. Below are the details:
Use Case
We have a requirement in our application to be able to split a claim via an API call. The workflow would look like this:
- New Claim Created
- We find and bring a new claim into our application (using ShortQuery)
- A user determines that the claim needs to be split
- The user clicks the Split Claim button in our application, selecting which procedures to split into a new claim
- We use the Open Dental API to request that the claim be split, passing the ClaimNum and the procedures that should be put in the new claim.
This request probably doesn't require a lot of extra details, but I'd like to just explicitly mention a few things to add clarity that would probably be a given anyway.
- The current Open Dental claim split code has validation that is run to ensure the claim and procedures are valid for splitting in the way requested. Our expectation is that Open Dental would still run this validation and return an error if we didn't meet the requirements of this validation.
- Upon success we would request that Open Dental returns the newly created ClaimNum for us to be able to easily find the new claim.
I am unaware of more than one set of code for splitting a claim in Open Dental, but in case there is some somewhere, I'll include our source code research to make sure we don't miscommunicate something.
After looking at the source, the initiating of the claim split is in OpenDental.FormClaimEdit.butSplit_Click. It does some validation, then the rest of the workload is handed off to the business layer, specifically OpenDentBusiness.Claims.InsertSplitClaim, to perform the split. This is the code we're referring to in our above request.
We really appreciate everyone's hard work on the Open Dental development team and how quickly they work to help fulfill API requests. I've been in software development for 22 years and I have never seen a company work so hard to prioritize API work like this. Please let me know if there are any questions that I can answer.