SRS > Use Case Suite > Use Cases

Release Information

Project: EGADSS
Internal Release Number: $Revision: 1.5 $
Related Documents:

UC-01: Start System

Summary: The System Administrator starts the system.
Priority: High
Importance for Product: High
Use Frequency: Sometimes
Direct Actors:
System Administrator
Main Success Scenario:
  1. start the system
  2. see confirmation that the system has been started successfully
Alternative
Scenario Extensions:
  • If the the system fails to start, an error message will be displayed to the System Administrator.
Use Case Dependencies:
  • Includes "UC-03: Load Knowledge Base"

UC-02: Shut Down System

Summary: The System Administrator shuts the system down when necessary.
Priority: High
Importance for Product: High
Use Frequency: Sometimes
Direct Actors:
System Administrator
Main Success Scenario:
  1. shut the system down
  2. see confirmation that the system has been shut down successfully
Alternative
Scenario Extensions:
  • If the the system fails to shut down, an error message will be displayed to the System Administrator.

UC-03: Load Knowledge Module

Summary: The System Administrator can load a knowledge module into the EGADSS knowledge base.  A knowledge module represent a group of guidelines related by subject, e.g. "immunization", "diabetes", "colon cancer prevention", etc.  EGADSS may simultaneously contain multiple knowledge modules. 

The default knowledge modules are also loaded automatically as the EGADSS system starts up.  Loading a new knowledge module does not clear existing modules already present in the knowledge base. 
Priority:
High
Importance for Product: High
Use Frequency: Rarely
Direct Actors: Knowledge Administrator
Prereq:
The EGADSS system must be started before this use case can proceed.
Main Success Scenario:
  1. request to load a knowledge module
  2. specify the knowledge module to be loaded
  3. see a confirmation that the load operation was successful
Alternative
Scenario Extensions:
  • If the the system fails to load the knowledge module, an error message will be displayed to the Knowledge Administrator.
Use Case Dependencies:
  • Is included in the "UC-01: Start System"

UC-04: Clear Knowledge Base

Summary: The Knowledge Administrator can clear the entire contents of the knowledge base.
Priority: Medium
Importance for Product: High
Use Frequency: Rarely
Direct Actors:
Knowledge Administrator
Main Success Scenario:
  1. request to clear the knowledge base
  2. see confirmation that the knowledge base has been cleared successfully
Alternative
Scenario Extensions:
  • If the the system fails to clear the knowledge base, an error message will be displayed to the Knowledge Administrator.

UC-05: Obtain Recommendations by a Simple Transaction

Summary: The EMR utilizes the EGADSS system functionality by providing a predefined extensive set of patient data to EGADSS and obtaining clinical recommendations in return.  This is facilitated by a simple 2-step transaction between EGADSS and the EMR.
Priority: High
Importance for Product: High
Use Frequency: Often
Direct Actors:
Prereq:
The EGADSS system must be started before this use case can proceed.
Main Success Scenario:
  1. request to obtain clinical recommendations
  2. provide an input document with extensive patient-specific information in a predefined format
  3. indicate that requests for additional patient information are not accepted
  4. obtain an output document with clinical recommendations (the document may contain zero or more recommendations)
Alternative
Scenario Extensions:
  • If the the EGADSS system fails to provide an output document, an error message will be communicated to the EMR.

UC-06: Remove Knowledge Module

Summary: The Knowledge Administrator can remove an individual knowledge module from the knowledge base.
Priority: Medium
Importance for Product: Medium
Use Frequency: Rarely
Direct Actors:
Knowledge Administrator
Main Success Scenario:
  1. request to remove a knowledge module from the knowledge base
  2. specify the knowledge module to be removed
  3. see confirmation that the knowledge module has been removed successfully
Alternative
Scenario Extensions:
  • If the the system fails to remove the knowledge module, an error message will be displayed to the Knowledge Administrator.

UC-07: View Knowledge Base

Summary: The actor can view the contents of the knowledge base which is loaded into the system.  Contents will be defined as knowledge modules that consist of guidelines listed by title, along with version and date uploaded to the system.
Priority: Low
Importance for Product: High
Use Frequency: Sometimes
Direct Actors: EMR, Knowledge Administrator, System Administrator
Prereq:
The EGADSS system must be started before this use case can proceed.
Main Success Scenario:
  1. request to view the knowledge base
  2. view the knowledge base contents
Alternative
Scenario Extensions
  • If the the system fails to disclose the knowledge base contents, an error message will be displayed to the actor.

UC-08: View System Configuration

Summary: The System Administrator can view the system configuration at any given time.
Priority: Low
Importance for Product: Low
Use Frequency: Rarely
Direct Actors:
System Administrator
Prereq:
The EGADSS system must be started before this use case can proceed.
Main Success Scenario:
  1. request to view the system configuration
  2. view the configuration information: version and deployment date of the overall system and individual key components (knowledge base, inference engine, etc).
Alternative
Scenario Extensions:
  • If the the system fails to provide its configuration information, an error message will be displayed to the System Administrator.

UC-09: Change Auditing Mode

Summary: The System Administrator can change the auditing modes of the system.  Two modes are "full audit mode" and "privacy mode".
Priority: Low
Importance for Product: High
Use Frequency: Rarely
Direct Actors:
System Administrator
Prereq:
The EGADSS system must be started before this use case can proceed.
Main Success Scenario:
  1. request to configure auditing
  2. view the current settings for the auditing mode
  3. make a selection for the desired auditing mode
  4. confirm the change of auditing mode
  5. see the settings with the new auditing mode
Alternative
Scenario Extensions:
  • If the the system fails to allow auditing configuration, an error message will be displayed to the System Administrator.
  • The System Administrator may cancel the auditing configuration operation at any time before confirming the operation.

UC-10: View Audit Log

Summary: The System Administrator can view the audit log of the system operations that relate to the processing of clinical knowledge and/or patient data, depending on the audit mode configuration.
Priority: Low
Importance for Product: High
Use Frequency: Sometimes
Direct Actors:
System Administrator
Prereq:
The EGADSS system must be started and the auditing must be configured before this use case can proceed.
Main Success Scenario:
  1. request to view the audit log
  2. view the audit log
Alternative
Scenario Extensions:
  • If the the system fails to provide the audit log, an error message will be displayed to the System Administrator.

UC-11: Obtain Recommendations by a Complex Transaction

Summary: The EMR utilizes the EGADSS system functionality by providing a predefined basic set of patient data to EGADSS.  EMR also indicates that EGADSS may request additional patient information from the EMR, if applicable.  Based on the provided patient information, EGADSS provides clinical recommendations back to the EMR.  This is facilitated by a complex multi-step transaction between EGADSS and the EMR.
Priority: Medium
Importance for Product: High
Use Frequency: Often
Direct Actors:
Prereq:
The EGADSS system must be started before this use case can proceed.
Main Success Scenario:
  1. request to obtain clinical recommendations
  2. provide an input document with basic patient-specific information in a predefined format
  3. indicate that additional patient information may be requested
  4. receive an output document.  The output document contains clinical recommendations (the document may contain zero or more recommendations) based on the patient information provided to EGADSS.  In addition, the document may contain the request for  additional/missing patient information. 
  5. provide an input document with the additional patient-specific information as requested by EGADSS.  The input document includes the originally send patient information and the requested additional information.
  6. receive an output document from EGADSS as in step 4 and continue transaction with EGADSS until no more patient information is requested or provided.
Alternative
Scenario Extensions:
  • EGADSS may not request any additional patient information if it does not need any to derive clinical recommendations.
  • EMR may stop providing patient information and stop the transaction when it does not wish or is not able to provide any more patient information.
  • If the the system fails to provide the audit log, an error message will be displayed to the EMR.
Use Case Dependencies:
  • Extends "UC-05: Obtain Recommendations by a Simple Transaction"

All text is available under the terms of the GNU Free Documentation License.

SourceForge.net Logo