News for hackers. Stuff that matters.
Re:TrueVault – HIPAA compliant data storage by hippaway on Thursday September 19, 2013 @02:09PM (#6413226)
hmmm, It made me realize that I may be on the verge of breaching the HIPAA laws. I'm developing an app on Google App Engine (which afaict won't sign a BAA), this app will help users with storing and interpreting their data (some of which may be considered health data: like all the biometric data). Anyone knows if I have to comply to HIPAA in spite of not being an health provider myself?
Re:TrueVault – HIPAA compliant data storage by jason_wang on Thursday September 19, 2013 @02:26PM (#6413321)
Take a look at this article: http://www.hhs.gov/ocr/privacy/hipaa/understanding/covereden...

The definition of who needs to comply with HIPAA has more to do with who has contact with protected health information and less about who the company is (e.g., a hospital or not).

Re:TrueVault – HIPAA compliant data storage by hippaway on Thursday September 19, 2013 @02:37PM (#6413380)
This document has some bullshit example: Identifying users by zipcode and gender? huh?

"Imagine that a covered entity is considering sharing the information in the table to the left in Figure 3. This table is devoid of explicit identifiers, such as personal names and Social Security Numbers. The information in this table is distinguishing, such that each row is unique on the combination of demographics (i.e., Age, ZIP Code, and Gender). Beyond this data, there exists a voter registration data source, which contains personal names, as well as demographics (i.e., Birthdate, ZIP Code, and Gender), which are also distinguishing. Linkage between the records in the tables is possible through the demographics. Notice, however, that the first record in the covered entity’s table is not linked because the patient is not yet old enough to vote."

Re:TrueVault – HIPAA compliant data storage by sp332 on Thursday September 19, 2013 @04:03PM (#6413882)
It's not bullshit. Here's the paper from 2000: http://dataprivacylab.org/projects/identifiability/paper1.pd... From the abstract: 87% (216 million of 248 million) of the population in the United States had reported characteristics that likely made them unique based only on {5-digit ZIP, gender, date of birth}.
Re:TrueVault – HIPAA compliant data storage by hippaway on Thursday September 19, 2013 @04:09PM (#6413925)
the date of birth is not cited in the example. Only the age. Seems like a stretch of an example to me.
Re:TrueVault – HIPAA compliant data storage by yannk on Thursday September 19, 2013 @02:31PM (#6413346)
This document states:

  "HIPAA defines a covered entity as 1) a health care provider that conducts certain standard administrative and financial transactions in electronic form; 2) a health care clearinghouse; or 3) a health plan"
which is explained by the flowchart in the document I linked in my other comment. So as long hippaway app doesn't take payments for health services (which you can't do unless you are a certified health provider), I guess she is fine. Yes?
Re:TrueVault – HIPAA compliant data storage by yannk on Thursday September 19, 2013 @02:25PM (#6413309)
According to: http://www.cms.gov/Regulations-and-Guidance/HIPAA-Administra...

As long as you don't accept payments you should be fine... But talk to your laywer? (Yeah I know...)

Re:TrueVault – HIPAA compliant data storage by hippaway on Thursday September 19, 2013 @02:33PM (#6413353)
I wish legal counsel was more easily accessible.
Re:TrueVault – HIPAA compliant data storage by NovemberWest on Thursday September 19, 2013 @04:01PM (#6413870)
If the data is stored on their device and you have zero access to it, I do not see any problem. Individuals have the right to do as they see fit with their own PHI.

Background: I paid insurance claims for over five years. Thus, I received HIPAA training annually. Feel free to email me.

Re:TrueVault – HIPAA compliant data storage by hippaway on Thursday September 19, 2013 @04:11PM (#6413935)
nah, data is stored in GAE. Thanks for your offer.