This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Permissions Catalog: Recommendations for Reuse"
Jump to navigation
Jump to search
Line 2: | Line 2: | ||
The permission catalog is a normative specification and it is [http://www.hl7.org/v3ballot/html/welcome/downloads/v3_rbac_2008SEP.zip available for download]. | The permission catalog is a normative specification and it is [http://www.hl7.org/v3ballot/html/welcome/downloads/v3_rbac_2008SEP.zip available for download]. | ||
− | *The most recently published permission catalog is [[20071112_HL7_RBAC_Healthcare_Permission_Catalog_v3_37.pdf]]. | + | *The most recently published permission catalog is [[Image:20071112_HL7_RBAC_Healthcare_Permission_Catalog_v3_37.pdf]]. |
Revision as of 19:03, 25 August 2008
The current Permissions Catalog for Role-Based Access Control specifies a set of normative permissions that specify operations that may be applied to a variety of object types.
The permission catalog is a normative specification and it is available for download.
- The most recently published permission catalog is File:20071112 HL7 RBAC Healthcare Permission Catalog v3 37.pdf.
The operations refer to the ability to append, create, read, update, delete, and execute specific "objects" identified in the RBAC standards. The "objects specify:
Permission | ||
Operation |
Object |
Effect |
append |
Administrative Ad-hoc Report |
A role that has this permission, allows the user that logs in with that role to append information to an existing ad-hoc administrative report. |
Healthcare Operations
- create
- revise
- activate
- complete
- suspend
- resume
- abort
- hold
- release
- cancel
- obsolete
- nullify