Onederful Partners with Principal Insurance to Automate Insurance Verifications
Let me describe the future of Eligibility & Benefits (E&B) verifications. Before a patient walks into a dental office, their Eligibility & Benefits are automatically checked with the Insurance Carrier, and that information is populated directly into the Provider’s software system.
The result is that there are: No surprise bills for the Patients, Providers can collect faster and save time with manual phone calls, and Insurance Carriers save millions on call center costs.
Sounds like an impossible reality right?
Today we announce the first step towards this reality. Onederful has partnered with Principal Insurance to enable 100% E&B information through an API to eliminate phone calls.
Onederful then standardized and transformed Principal’s E&B data to enable our network of Software Clients to easily connect to it.
The Onederful network of top Practice Management Software Companies, Dental Services Organizations (DSOs), Outsourced Billers, Dental Offices and Insurance Experts provided feedback that they could receive close to 100% of E&B information when verifying patients, thereby eliminating a 30+ minute phone call to the carrier. Data such as full patient history, procedure code limitations, downgrades, and missing tooth clauses were all available through the API.
Principal Insurance is the first of many carriers we are partnering with to automate insurance verifications. We are building a new ecosystem to transform the dental industry. If you are an Insurance Carrier interested in partnering with Onederful to eliminate phone calls, please reach out to email@example.com.
Onederful announces that the company has undergone a System and Organization Controls (SOC) 2 examination resulting in a CPA's report stating that management of Onederful maintained effective controls over the security, availability, and confidentiality of its system. The engagement was performed by BARR Advisory, P.A.
A SOC 2 report is designed to meet the needs of existing or potential customers who need assurance about the effectiveness of controls at a service organization that are relevant to the security, availability, or processing integrity of the system used by the service organization to process customers’ information, or the confidentiality or privacy of that information.
The following principles and related criteria have been developed by the American Institute of CPAs (AICPA) and the Canadian Institute of Chartered Accountants (CICA) for use by practitioners in the performance of trust services engagements:
- Security: The system is protected against unauthorized access (both physical and logical).
- Availability: The system is available for operation and use as committed or agreed.
- Confidentiality: Information designated as confidential is protected as committed or agreed.
- HIPAA Security Rule Requirements: The BI360 system and applicable controls are compliant with the applicable HIPAA Security Rule requirements set forth in the U.S. Department of Health and Human Services’ (HHS) Health Information Portability and Accountability Act
If you represent a Dental Insurance carrier and would like a copy of our SOC 2 report, please contact us at: firstname.lastname@example.org.
Our team is happy to introduce our revamped developers webpage.
In this update we've created new:
- API Documentation
This revamped API documentation showcases our APIs and schemas as well as descriptions for each parameter used.
Payer list search functionality to search through the 200+ dental payers supported by Onederful.
Blog is where our team will announce new features we're rolling out.
Our team is also currently working on a couple quickstart tutorials that we will release soon. If you have any feedback for our team about our revamped docs, please feel free to email us at email@example.com. We greatly appreciate your feedback!
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 firstname.lastname@example.org. We greatly appreciate your feedback!