171–180 of 192 posts
All this legal bullshit could have been avoided if this was a program for people to run on their own computers. Why oh why is this being run as a service?
As another commenter commented, this would be a good candidate for a local-first app. I'd love to do that at some point.
Tomorrow I will take down the HN front page. Your accounts will remain in case you still want to check things out. You can also delete your accounts yourself, or ask to have them deleted.
If you want, you will still be able to create a new account from the default main page https://katesapp.org. You will need to ask for an access code, but I'm happy to provide one.
Edit: Sorry, the option to delete your account has not been uploaded to the server yet. However, email me at the address in my HN account, or contact me through the app, and I'm still happy to delete your account for you if you want. Again, thank you everyone.
I wouldn't worry too much about what a lot of the comments are saying. I would heed some of the advice about being secure but I wouldn't worry too much about it being a problem or shutting down the app until you have it worked out. I don't want to discourage you because it's always good to have multiple options but I would look at what Cariloop ( https://cariloop.com ) is doing, try and focus it like that but with un…
It looks like Cariloop advises people on how to find medical assistance, is that correct? Is there someplace to get more specific information?
Earlier quoted context omitted.
I don't read others' warnings as fear mongering. Rather, they are genuinely offering concrete steps to be taken to avoid problems that frequently arise in this domain. "Go talk to a lawyer" is not an attempt to scare or some impossible abstract advice. It's a very concrete, and very reasonable step that really ought to be taken early on in this effort. Maybe everyone here is off base. How might the app developer dete…
Maybe fear mongering is overstating but... Speaking to a lawyer is not the first step when building something in this domain (unless you already have someone bankrolling you). In this case there's an app that this guy built for families to use. It's obviously in it's infancy. The helpful advice here would be about posting that this is in beta or maybe reading the HIPAA guidelines and ensuring that he's adhering to th…
If you're dealing with personal health information (PHI), I would advise you to temporarily close your site and hire a lawyer straight away. Whenever you touch this kind of data, regulatory regimes like HIPAA may apply, and you need to be extremely careful. There's not a HIPAA compliance or even a privacy policy statement available on your front page. See https://www.hhs.gov/hipaa/for-professionals/privacy/laws-reg..…
It sounds like a useful app but only if it can be safe. Which I don't belive it can become with a classic web2.x startup approach.
If you're dealing with personal health information (PHI), I would advise you to temporarily close your site and hire a lawyer straight away. Whenever you touch this kind of data, regulatory regimes like HIPAA may apply, and you need to be extremely careful. There's not a HIPAA compliance or even a privacy policy statement available on your front page. See https://www.hhs.gov/hipaa/for-professionals/privacy/laws-reg..…
> Whenever you touch this kind of data, regulatory regimes like HIPAA apply, My understanding is you're an actual attorney, yes? Can you shed any light on this area...? My understanding is HIPAA and similar laws aren't applied as a result of a user disclosing their own information for their own purposes. For example, you can freely put your own personal medical information into Google Docs, Apple Notes, Facebook post…
Let the data stay client side. Facilitate secure client-to-client communication instead of relying on the gravity well of cloud servers.
It becomes a lot more light-weight, and if done right the rules and red-tape do too as you reduce your presence in the regulatory scope by verifiably preventing access to user data by yourself (and service providers, their partners, hackers, and three-letter agencies).
Earlier quoted context omitted.
A business associate to who? The user?
A covered entity (eg. doctor, nurse, etc.)
If you're dealing with personal health information (PHI), I would advise you to temporarily close your site and hire a lawyer straight away. Whenever you touch this kind of data, regulatory regimes like HIPAA may apply, and you need to be extremely careful. There's not a HIPAA compliance or even a privacy policy statement available on your front page. See https://www.hhs.gov/hipaa/for-professionals/privacy/laws-reg..…
Then/or refactor out server-side storage. These concerns don't surface in the same way if you never touch the data. It sounds like a useful app but only if it can be safe. Which I don't belive it can become with a classic web2.x startup approach.
Earlier quoted context omitted.
A covered entity (eg. doctor, nurse, etc.)
How could this app possibly be considered a business associate to a provider? The provider has no idea it’s even being used, let alone a formal association with the application.
The landing page doesn't make it clear whether providers are expected to use it or not.
Earlier quoted context omitted.
A covered entity (eg. doctor, nurse, etc.)
How could this app possibly be considered a business associate to a provider? The provider has no idea it’s even being used, let alone a formal association with the application.