IT304Module3
docx
keyboard_arrow_up
School
Southern New Hampshire University *
*We aren’t endorsed by this school
Course
304
Subject
Industrial Engineering
Date
Dec 6, 2023
Type
docx
Pages
8
Uploaded by CorporalSummerOryx26
Courtney Angran Southern New Hampshire University IT 304 Systems Requirements/Implementation Plan
Instructor Daniel Koch
12/11/2023
Module 3 Activity: Use Case Diagrams and Specifications
Receptionist or Kiosk
Appointments made by computer or mobile device
Notification for Pharmacist & system updates
Bring Medical Record up to date
Doctor Examines Patient
Nurse performs physical exam and updates patient record
Insurance or Co-
payment fee
Confirmation of appointment
Biography & Purpose
Patient
Director
Provider of Insurance
Payment Options
Capture Patient Information/Reason for Visit
Use of Case Specific Components
Responses
Use Case Number
What is the # of the Use Case?
1
Use Case Name
What is the name of this Use Case?
Collect information from patients and reason for visit.
Actor
Who is involved?
Patient, Director, and Provider of Insurance.
Summary Description
What happens in this Use Case?
Patients' data becomes synchronized across all systems.
Priority & Importance
Importance of Use Case? Primary- Major Process, Secondary- Minor Process
To prevent errors, it is essential to keep track of patient visits across all systems.
Relationships between Use Cases
Which actors does this Use Case interact with?
Patient, Director, and Provider of Insurance. Trigger
What starts the Use Case?
Appointment initiated by patient. Pre-Condition
What happens before the Use Case begins?
Appointment has been established. Post- Condition
What happens after the Use Case ends?
File/ Appointment will be closed out.
Path
Path of Process? What is the main success scenario that should be documented? Document variations as extensions or as included use cases.
Next steps are to ensure that the patients’ visit, and medical history have been accurately documented and are up to date across all systems. Non-Functional Requirements
What are the non-functional requirements of the use case?
Dependability of the systems in play.
Verify Patient Insurance
Send an Insurance Claim Form
Received and Confirmed
Denied Insurance Claim
See Doctor and/or Nurse
Payments are submitted
Approved Insurance Claim
Director
Provider of Insurance
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
Use of Case Specific Components
Responses
Use Case Number
What is the # of the Use Case?
2
Use Case Name
What is the name of this Use Case?
Verify Patient Insurance
Actor
Who is involved?
Patient and Provider of Insurance
Summary Description
What happens in this Use Case?
Insurance Providers check and validate the details
of the patient's PII prior to approving it.
Priority & Importance
Importance of Use Case? Primary- Major Process, Secondary- Minor Process
Providing better patient care means that doctors should be properly set up to provide that wanted care as well as honestly compensated for expertise.
Relationships between Use Cases
Which actors does this Use Case interact with?
Director and Provider of Insurance
Trigger
What starts the Use Case?
Patient attends an appointment or visits the doctor's office.
Pre-Condition
What happens before the Use Case begins?
Patient has appointment with a physician.
Post- Condition
What happens after the Use Case ends?
The case is resolved, payments are made to the doctors. Path
Path of Process? What is the main success scenario that should be documented? Document variations as extensions or as included use cases.
Check if patient visits are covered by insurance coverage so that claims are more likely to be approved and processed. Non-Functional Requirements
What are the non-functional requirements of the use case?
Systems Performance
Capture Patient Copay
Check status of the Copay
Submit copay prior to visit
Receive payment
Visit Doctor and/or Nurse
Approved to see the doctor
Submit copay after payment
Director
Patient
Use of Case Specific Components
Responses
Use Case Number
What is the # of the Use Case?
3
Use Case Name
What is the name of this Use Case?
Capture patient copay.
Actor
Who is involved?
Patient and Provider of Insurance.
Summary Description
What happens in this Use Case?
Verifying copay prior to seeing doctor.
Priority & Importance
Importance of Use Case? Primary- Major Process, Secondary- Minor Process
Copay is determined by the patient’s insurance policy. Copay is not always required for each appointment. Relationships between Use Cases
Which actors does this Use Case interact with?
Patient and payment options.
Trigger
What starts the Use Case?
Patient is responsible for copay
Pre-Condition
What happens before the Use Case begins?
Patients schedule a time to see a doctor.
Post- Condition
What happens after the Use Case ends?
If payment is required ensure the completion of documenting the payment, doctors visit is completed.
Path
Path of Process? What is the main success scenario that should be documented? Document variations as extensions or as included use cases.
Verification and processing of any needed copays.
Non-Functional Requirements
What are the non-functional requirements of the use case?
Integrity of Data
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
Schedule Next Appointment
An Appointment Online
Kiosk or Receptionist
Make Phone Call
Confirming Appointment
Confirming Provider of Insurance
Document Reason for visit
Verify Patient Information
Appointment Confirmed
Patient
Director
Use of Case Specific Components
Responses
Use Case Number
What is the # of the Use Case?
4
Use Case Name
What is the name of this Use Case?
Schedule patient next appointment
Actor
Who is involved?
Patient and Director
Summary Description
What happens in this Use Case?
Appointment scheduling is done online, by phone, in person or through the website. Priority & Importance
Importance of Use Case? Primary- Major Process, Secondary- Minor Process
Simple, patients make the appointment, however,
they are not necessarily required to show up to the appointment.
Relationships between Use Cases
Which actors does this Use Case interact with?
Patient and Director
Trigger
What starts the Use Case?
Scheduling appointments when needed
Pre-Condition
What happens before the Use Case begins?
Patient schedules appointment with the doctor staf
Post- Condition
What happens after the Use Case ends?
Patient confirms confirmation and reminder of their visit
Path
Path of Process? What is the main success scenario that should be documented? Document variations as extensions or as included use cases.
Validate appointments with doctor's schedule and authenticate insurance coverage. Non-Functional Requirements
What are the non-functional requirements of the use case?
Dependability