This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Consent Directive Use Cases

From HL7Wiki
Jump to navigation Jump to search

Role-Based Access

The following use cases are based on the RBAC specification.

Each type of user in a healthcare organization has a specified "role" which consists of "permissions" to perform certain functions and access specific data. While the set of permissions assigned to each role is based on local policy (enterprise-wide, jurisdiction-wide, etc.), the operation and the functions/information to which they apply, are standardized by HL7 as a normative specification. The functional roles for healthcare users are specified as an informative specification.

Mask Functionality

Based on the functional role of the user logged in, the healthcare information system will limit access only to those operations (e.g. create, read, update, delete, execute) and functions (identified using an object id) that are allowed for that role.

Basic scenario

A user logs in, the application identifies the functional group or role for the user. Based on the user's role, the application interrogates the security systems for the functions allowed for the role. The security system stores the permissions associated with the role and it can specify whether the user can access specific functionlity. Based on the results provided by the security system, the application displays to the users only those are of functionality that their functional role in the allows them to have. This use case would apply to a situation where both the application and the security systems are in the same organization or in different organizations.

=Actors

  • User
  • Healthcare Application
  • Security System

Mask Information

Based on their functional role, users can view(read),create, update, delecte, or act (execute) on information contained in a patient's record. While the role of the user may limit their access to specific patient record information - limiting it to the information required to perform the job as specified by the role -

Consumer Preferences

Consumer Manages Consent Directives

This use case assumes that the consumer has access to a Personal Health Record system through some type of portal (e.g. web) and manages a single data consent intentended to be shared with a variety of providers, payers, etc.