Emergency Department View - SENG-350-2024-fall/Team-11 GitHub Wiki

Emergency Department (ED) Staff View

Primary Presentation:

• Diagram: The ED staff view would include the ObserverImplementation class to receive real-time patient updates. The ED staff reviews the symptom evaluation and makes final treatment decisions.
• Notation: UML Use Case Diagram.

Element Catalog:

• ObserverImplementation: Manages updates from the NewPatient subject and notifies ED staff of new evaluations.
• NewPatient: Represents new patient entries in the system, which trigger notifications to the ED staff.
• PrescriptionService: Manages the final submission of prescriptions based on evaluation.

Context Diagram:

• Context: The ED staff is notified whenever a new patient enters the system, which happens when the patient submits their symptom evaluation.
• External Entities: Patient, GP (for feedback).

Variability Guide:

• Variability: ED staff have the ability to override recommendations based on additional clinical context. This happens at runtime and may be based on available resources.
• Runtime Variability: Based on patient condition, the recommendation can be modified in real-time.

Rationale:

• Rationale: The design allows ED staff to receive up-to-date patient information and override recommendations as needed. This is crucial in high-pressure environments where timely information is critical.
• Rejected Alternatives: The idea of static patient data without real-time updates was rejected.

Related Views:

• Parent View: Overall system view (Mister ED).
• Refined Views: Patient evaluation and prescription submission.