Use Case Description—OMaR Project
| Use Case Name: | Verify Security Permissions |
| Use Case Purpose: | The purpose of this use case is to verify that the actor requesting access to Clinical Records information is permitted to have access to such information. This use case is “included” in other use cases. |
| Point of Contact: | |
| Date Modified: | |
| Preconditions: | None identified. |
| Postconditions: | None identified |
| Limitations: | None identified. |
| Assumptions: | None identified. |
Basic Flow:
| A. | The actor enters identification information. |
| B. | The actor's identity is verified. |
| C. | The actor's permission set is retrieved. |
| D. | The actor's permission set is provided to the “including” use case. |
Alternate Flow:
Condition Triggering Alternate Flow: OMaR does not recognize the ...
Get UML for Database Design now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
