Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kategleason
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
31.
▲
by
kategleason
14y ago
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 fo
32.
▲
by
kategleason
14y ago
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
33.
▲
by
kategleason
14y ago
weeee github is back up!
34.
▲
Show HN: Demo application for Eligible Web Services.
(github.com)
47 points
by
kategleason
14y ago
|
21 comments
35.
▲
by
kategleason
14y ago
love this team, congrats!
36.
▲
by
kategleason
14y ago
great work.
37.
▲
Why we built a REST API for healthcare eligibility.
(youtube.com)
5 points
by
kategleason
14y ago
|
0 comments
38.
▲
by
kategleason
14y ago
loved reading this. thanks for sharing it.
39.
▲
Peer Networks and Health Innovation
(speakerdeck.com)
27 points
by
kategleason
14y ago
|
1 comments
40.
▲
by
kategleason
14y ago
That is a good point in comparing Idaho to MA housing and pricing costs. But then how can you justify California's low insurance monthly rates (before the new hikes that just happened this month) California: $157
41.
▲
by
kategleason
14y ago
It was cited because health care plans are not sold by gender. Therefore the plan's actuarial risk assessment needs to account for maternity whether or not the person signing up for the plan is a male or female.
42.
▲
by
kategleason
14y ago
It is my understanding that one of the most cited justifications for passing healthcare reform was to lower costs. Specifically, the monthly cost for individuals who need to purchase their own health insurance plans.
43.
▲
Health insurance rate hikes. Why so surprised?
(katgleason.tumblr.com)
16 points
by
kategleason
14y ago
|
11 comments
44.
▲
by
kategleason
14y ago
amazing.
45.
▲
by
kategleason
14y ago
nice :)
46.
▲
by
kategleason
14y ago
Thanks for saying we make you want to reboot project :)
47.
▲
by
kategleason
14y ago
really enjoyed this read.
48.
▲
by
kategleason
14y ago
Congrats!
49.
▲
by
kategleason
14y ago
Very cool Dennis, I'd love to connect with you to hear more about your experience. Please email me k@eligibleapi.com
50.
▲
by
kategleason
14y ago
Engineering is transparent … It is fairly easy to evaluate how good someone is. Are they a good coder? An ubercoder? Things are different with sales. Sales isn’t very transparent at all. We are tempted to lump all salespeople in with vacuum
51.
▲
by
kategleason
14y ago
that's my hood!
52.
▲
by
kategleason
14y ago
implemented! thanks.
53.
▲
by
kategleason
14y ago
I love this idea.
54.
▲
by
kategleason
14y ago
Thanks Mike. We are starting at the source and will not leave it until there is a genuine shift in how eligibility for healthcare is handled.
55.
▲
by
kategleason
14y ago
You're twisting my words. I'll let you refer to our terms, security and privacy for the rest of your questions.
56.
▲
by
kategleason
14y ago
No need to get rude here. My replys are sticking to facts not insults. Yes, my experience is in sales and I'm proud of it. Here's the data most interesting to our existing user base: 1) limitations (ie if the patient only has certain amoun
57.
▲
by
kategleason
14y ago
Gotcha, primary care is what I assumed. Most of the insurance company websites will give you back a basic active/inactive response along with the patient's copayment. For primary care docs this is enough (although its still annoying to go
58.
▲
by
kategleason
14y ago
You forgot to mention what specialty you are? Take a look at our privacy, terms of service, and security pages to answer the rest of your questions above. If you do not think the service is useful then you don't need to use it. That's the
59.
▲
by
kategleason
14y ago
Nope, sorry we do not handle 837 or 834 EDI transactions at this time.
60.
▲
by
kategleason
14y ago
I see. We certainly would not expose your patient's data. My reply at bottom should help clear that up for you. You forgot to mention what specialty you are?
More ›