|
|
|
|
|
by throwawaymath
2734 days ago
|
|
Before writing any code you should seek to deeply understand the problem space of authentication and authorization. HIPAA compliance is primarily an authorization problem, not an authentication problem. That is: both are important, but the unique set of challenges within the scope of HIPAA have to do with authorization of read/write access to data, not authentication. Authentication asserts identities. Authorization asserts capabilities. This shifts and compartmentalizes the problem somewhat. Almost all interactive applications need to support robust authentication, but most applications do not require the sophisticated authorization restrictions HIPAA demands. Whatever it is you choose, you should: 1) Use a mature, reputable library; 2) Use a library which provides the simplest possible interfaces for solving your needs in the most turnkey manner; 3) Engage with a reputable consulting firm specializing in HIPAA compliance and application security. I would also recommend reading through as much information about Aptible's architecture and design ethos as possible. They have done an excellent job of navigating this problem space. |
|