Our team is happy to introduce v2 eligibility and benefits API to the dental industry. After spending countless hours listening to client feedback, talking to insurance companies, and working with clinical and engineering teams, we've taken all our learnings and used them to improve our eligibility and benefits API.
We've recently updated our API developer documentation to provide more transparency and description to the underlying schema as well as provide enums used.
The main challenge with working with insurance data is that each insurance has their own language and way of structuring data, meaning there is no normalized structure across all the insurances. This causes issues at the integration level as that requires mapping and translation at a per insurance company level.
Internally, over the last couple years, Onederful has been codifying and essentially structuring data on a per insurance level to limit the scope and variability across insurance companies. Onederful's v2 eligibility and benefits API is meant to provide a universal schema to normalize data across insurance carriers.
As this has never been done in the industry before, there is still room for improvement as there are still free text sections that can be codified and placed into enums. However, with the help from you as client feedback, we can constantly improve our API and together work towards codifying across all insurances in the dental space.
If you come across any free text sections that you believe should be codified into an enum, please reach out to us at email@example.com. We greatly appreciate your feedback!