Significance and Use 4.1 This guide has three purposes: 4.1.1 To serve as a guide for developers of computer software that provides or makes use of authentication and authorization processes, 4.1.2 To serve as a guide to healthcare providers who are implementing authentication and authorization mechanisms, and 4.1.3 To be a consensus standard on the design, implementation, and use of authentication and authorization mechanisms. 4.2 Additional standards will define interoperable protocols and message formats that can be used to implement these mechanisms in a distributed environment, using specific commercial technologies such as digital signatures.Scope 1.1 This guide covers mechanisms that may be used to authenticate healthcare information (both administrative and clinical) users to computer systems, as well as mechanisms to authorize particular actions by users. These actions may include access to healthcare information documents, as well as specific operations on those documents (for example, review by a physician). 1.2 This guide addresses both centralized and distributed environments, by defining the requirements that a single system shall meet and the kinds of information which shall be transmitted between systems to provide distributed authentication and authorization services. 1.3 This guide addresses the technical specifications for how to perform user authentication and authorization. The actual definition of who can access what is based on organizational policy.
