Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I dread the idea of having to navigate the current US healthcare system in circumstances like that.

One drawback that occurs to me about the idea of projecting lifespan/healthspan is that with the data you'd need, you get into PHI territory pretty quickly right?



What opensocialsecurity[0] does is sufficient for most folks. Mike has a choice of five different mortality tables.

[0] https://github.com/MikePiper/open-social-security/blob/maste...


Letting the user pick from preset mortality tables seems like a pretty sensible approach to me. Thanks for the link; bookmarked!


Yeah that's probably protected data. I'm not a lawyer but maybe it could still work if you don't store the health data and just use it to locally generate adjustments (or maybe just store the health parts in-browser but keep the generated financial adjustments in the cloud). The more accurate your projection model, the more personal data it'll have to factor in.


Anyone happen to know what the standard is for when something officially counts as data collection? i.e. do you always have to send things sever-side before it counts? With all the fuss about things like cookies, I wouldn't even be that surprised if a form input that went nowhere could somehow still get you in trouble.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: