IHERO UseCase User Authentication

1. Proposed Workitem: User Authentication

• Proposal Editor: C.Field
• Editor: C.Field
• Date: N/A (Wiki keeps history)
• Version: N/A (Wiki keeps history)
• Domain: Radiation Oncology and IT

2. The Problem

Account authentication (e.g. username, password) is becoming increasingly difficult to manage both from a user perspective because of the requirement to have usernames and passwords for a variety of systems and applications; and for administrators who must maintain these various systems and applications.

3. Key Use Case

The problem: A radiation therapist comes in to work and turns on the treatment workstation computer, username1/password1 is required. Another general purpose computer is turned on: username2/password2 is required. A treatment application (e.g. scheduling, charting, …) is started up, username3/password3 is required. The first patient is treated and an interrupt occurs, username4/password4 is required to clear the interlock. The user switches to the general purpose computer to read email: usernname5/password5 is required. During the day, the therapist moves to another treatment unit to cover coffee breaks and must clear another interlock; username6/password6 is required.

The solution: Identical scenario as above, except each system and application authenticates the user against the same authentication system. All usernames and passwords would be identical, and the authenticating system would maintain access rights for the various systems and applications. A backup authentication system would be a requirement, in case the primary system failed.

4. Standards & Systems

All systems and applications inside and even outside the Radiation Oncology domain.
Standards ???

5. Discussion

All existing and new actors, transactions, profiles would authenticate with a common authentication system.