I'm a health care informatics professional (mostly clinical, not billing) and I can't seem to divine it.
I'm a health care informatics professional (mostly clinical, not billing) and I can't seem to divine it.
There are ANSI standard EDI transactions designed specifically for healthcare insurance eligibility inquiries (there also exists transactions for claims, but that's the other side of the puzzle). The standards themselves are pretty simple. But unfortunately, from a business development and integration perspective, the effort required to become trading partners with healthcare insurance companies is extremely high. There are plenty of vendors and clearinghouses out there which make the process easier. But this company is trying to make the setup and integration even easier with self-service sign-up and credit card billing. It's a novel idea.
Edit: I have no affiliation with Eligible but I've been working with the underlying technology for many years.
It does look very useful :)
Before a test or lab is ordered, or before a specialist visit is scheduled, one of the assistants needs to verify that your insurance will actually cover the procedure. Typically this means the assistant needs to call the insurance provider, give them your information and what procedure(s) they are checking on.
Insurers provide this data but there are close to a dozen disparate standards and formats. Eligible consolidates all that into a REST API that developers can build applications on top of. From what I can tell this is definitely not for the healthcare industry, but for our industry to build healthcare applications.
I have no affiliation with Eligible, but I've been working in healthcare IT for several years, although not at the startup level.
Also, I'd advise you not to jump straight to messages about "non-technical bureaucracies." It's certainly true in some cases, but it sounds derogatory. Better to address the objectives these people are trying to meet.
They provide a RESTful API to insurance eligibility data, which is useful because the current (required-by-law) APIs are horrendously complicated and difficult to work worth, AND they're disparate, varying by vendor.