hipaa-compliance-developers-guide
wyhash
Our great sponsors
hipaa-compliance-developers-guide | wyhash | |
---|---|---|
7 | 9 | |
1,627 | 913 | |
0.1% | - | |
0.7 | 6.6 | |
about 1 year ago | 3 months ago | |
C | ||
- | The Unlicense |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
hipaa-compliance-developers-guide
-
Show HN: Using GPT-3 and Whisper to save 40% of doctors’ time
No. HIPPA applies to software.
"If you handle, store or transmit protected health information (PHI) to or from a covered entity then you need to be HIPAA compliant."
Source: https://github.com/truevault/hipaa-compliance-developers-gui...
-
Need help on getting Android app HIPAA compliant
I recommend this as a starting place: https://github.com/truevault/hipaa-compliance-developers-guide
-
Backblaze submitting names and sizes of files in B2 buckets to Facebook
It depends on the relationship the third party has with the 1st party.
https://github.com/truevault/hipaa-compliance-developers-gui... was on HN a week ago. It seemed to jive pretty well with our internal policies at the HIPAA compliant company I work for.
-
Hacker News top posts: Mar 15, 2021
A developers guide to HIPAA compliance\ (57 comments)
- A developers guide to HIPAA compliance
wyhash
- Wyhash: The fastest quality hash function
-
What hash function you use for hash maps / hash tables?
I recently switched to wyhash as it seems to have a good combination of speed and stability.
-
Are there any weaker hashes than MD5, but still randomly distributed?
wyhash is a decent option for if you don't need a cryptographical quality hash
-
Hacker News top posts: Mar 15, 2021
New Bare Hash Map: 2X-3X Speedup over SOTA\ (32 comments)
-
New Bare Hash Map: 2X-3X Speedup over SOTA
I feel like you’d want something a bit safer than “we don’t store the keys and just rely on the hash to be really good” [1], putting “please do not use this for serious tasks” in a comment embedded in the header file isn’t a clear enough warning.
It’s not clear to me that that probability of collision assumptions hold. It’s basically assuming that the hashing is perfect and distributes any inputs to the full 64-bit space with uniform probability. That’s the usual hash map / randomized algorithm hope, but does BigCrush or similar avalanche testing really prove that? (Presumably not, otherwise there wouldn’t be image attacks for things like md5).
[1] https://github.com/wangyi-fudan/wyhash/blob/d2a305811972f391...
- wyhash and wyrand are a non-cryptographic 64-bit hash function and PRNG respectively