22 comments

[ 3.1 ms ] story [ 58.9 ms ] thread
If you don't believe in easy eligibility integration yet, prepare for the magic show.
Just so happens this hits #1 on HN just as GitHub has a major service outage... https://status.github.com/
Well, can someone explain what this is about in the meantime?
Eligible is a Health Information API that launched last summer (YC S12, I think). This sample app is a basic demonstration of the API's ability to instantly show patient eligibility information for specific medical procedures. Prior to their API one would have to call insurers and other groups to verify eligibility, rates, etc. They are doing some very cool stuff to normalize health data across many different systems.

They also used to have a consumer app to do this.

Got it working after some refreshing. Getting errors while trying to make it work locally, though.

The read-only demo is at http://eligible-demo.herokuapp.com/.

Not that I understand what this is supposed to be about, though.

Feel free to post details on any errors. Issues page on github is probably the best place, once it's back up.
I really really have no idea what this thing is about. Can someone explain please?
Instant integration with over 700 health insurance companies across the country. Healthcare companies use us to query for real time information on their patient's benefit plans. eligibleapi.com
Eligible is an awesome service. We plan to use it in our up coming product .. Keep up the good job !
For a number of common health insurance transactions (verifying/checking health insurance information for a patient, procedure eligibility, patient demographics, claims status) that are part of the standard HIPAA transaction set, Eligible replaces legacy X12 EDI with a modern API.

Basically, if you are building any healthcare tools that could use administrative information from a health insurance company, you should probably be doing it on Eligible's platform.

http://eligibleapi.com

Not related to the project itself but with Eligible. Not sure if the author is related to them.

I just checked their pricing page.

Why the hell do they have this in a threatening wording:

* If you force us to apply pass-throughs we will contact you.

First, why use the * ? I scanned the damn page trying to find out where the * was on the text.

Second, 'if you FORCE us ... we WILL contact you'. I don't even know what pass-through is but honestly, I feel I'm already under scrutiny even before using them.

Save it for the FAQ or Terms of Service.

yeah the wording is my fault. I'll update it now. What I should have wrote is: "if you're using us exclusively for medicaid transactions, we'll contact you"

the reason being is because we actually get charged some govt pass through fee for medicaid transactions right now. for all our other customers the volume is low enough where we just take the loss, but for those only planning to ping medicaid companies it would not be worth it to us.

Even so, why not 'If you would like to use us exclusively for medicaid transactions, contact us at' or something like that?

Your wording just seems you will be keeping an eye on what I'm doing and if I screw up you will get in contact with me and not in a good way.

In any case, congratulations on the service, I hope it goes well for you guys.

Makes sense.

Thanks for being constructive with the feedback :) just pushed the update and took your advice on wording.

No problem and good luck! :)
how does this jive with RBM's? Are you even including radiology related service codes?
There we go, then I refer back to my original question(RBM's). I commented on this a while back on another thread. But radiology is where the big $$ is. Any plans to go look into this.
As someone who once worked in this space (Specifically hospital HIMS), you had me at HL7. :)