OneID and Meaningful Use Stage 2 Standards and Certification If you are architecting a solution using old-fashioned identity and identity paradigms, it is really hard to design a solution to the meaningful use requirements. But once you have a trustable general purpose bring your own identity (e.g., OneID) that inherently guarantees privacy and security and provides end-to-end security with digital signatures and is capable of securely and privately storing digital certificates, etc., then everything (such as identity management, identity proofing, and role based access control) becomes MUCH easier to architect a strong, but very usable system where a patient and physician can have a single identity for all systems. So OneID can be very useful as an identity paradigm to use rather than existing centralized IdP models or having each module implement its own security. OneID is much more than just authentication. You can store certificates in it, use if for digitally proving assertions, store user and RP-defined attributes, etc. So it opens up a whole new way to think about identity management and RBAC that has not be available before. See also:OneID documentation guide |