From the given case study, please help me with making a detailed events table and a Use Case diagram based of it.

I will provide the following images for your reference: Case Study, Question, and Rubrics

Case Study Eastgate Health Co-Dp Ltd Administrative System Eastgate Health Co-Dp Ltd Is a not-for-pro'flt, member owned co- operative that provides affordable medical and healthcare services to the communities where it operates. Eastgate Health Co-Op hosts a number of doctors [GPs and specialists} and nurses t that Ioolt after patients. For administrative purposes, Eastgate Health needs an IT system that processes patient administration records [not actual medical records}. Each patient has a record _ with his or her name, gender, date of birth, date of first visit, and date of fast visit. Patient records are grouped together under a household. A household has attributes such as name of head of household, telephone number, and address. Each household is also associated with an insurance carrier record, containing name of Insurance company, address, billlng contact person, and telephone number. At Eastgate Health Coop, each medical staperson aiso has a record that tracks who works with a patient tdoctor, nurse, medical technician}. Because the system focuses on patient administration records, only minimal Information Is kept about each medical staff person, such as name, address, and telephone number. Information Is maintained about each office visit, such as date, insurance oopay amount lamount paid by the patient}, paid code, and amount actually paid. Each visit is for a single patient, but, of course, a patient will have many office visits in the system. During each visit, more than one medical staff person may be Involved by doing a procedure. For example, the medical technician, doctor, and nurse may all be Involved on a single visit. In fact, some doctors are specialists In certain medical fields; even multiple doctors may be Involved with a patient. For each staff person that does a procedure In a visit combination [many-tomanyl, detalled Information is kept about the procedure. This Information Includes the type of procedure, a description, the copay amount, the total charge, the amount paid, and the amount the Insurance company denied. Another domain that the system will need to keep track of relates to invoicing. There are two types of Invoices: invoices to Insurance companies and lnvoioes to heads of household. Both types of Invoices are fairly similar, listing each visit, the procedures Involved, the patient copay amount, and the total due. Obviously, the totals for the are different from the patient amounts owed. Even though an invoice Is a reportiwhen printed}, It also maintains some Information such as date sent, totai amount, amount aiready paid, amount due and the total received, date received, and total denied. The latter Is relevant because insurance companies do not always pay the full amount they were billed for. Information about patient and headofhousehofd Information, will be entered and kept up to date in the system by the receptionist. The receptionist will also keep track of office visits by the patients. Patient Information Is also entered and maintained by the office business manager. In addition, the business manager maintains the information about the medical staff. Another responsibility of the business manager is to print the invoices. Patient invoices are printed monthly and sent to the head of household. Insurance invoices are printed weekly. When the invoices are printed, the business manager double-checks a few invoices against information in the system to make sure it is being aggregated correctly. When payment is received, s/he also enters this information in the system. Medical staff are responsible for entering information about the medical procedures they perform. The business manager also prints an overdue invoice report that shows heads of household who are behind on their payments. Sometimes doctors like to see a list of the procedures they performed during a week or month, and they can request that report.3) To what events must the Eastgate Health Co-Op Ltd Administrative System respond? List each event, the type of event, and the resulting use case. Be sure to consider all the use cases that would be needed to maintain the data in the system, thinking in terms of the CRUD technique. (Use the provided table to assist you. If you need more rows, add them.) Event Type Use case Office Business Manager edits External Maintain medical staff medical staff information Receptionist enters office visit External Record office visit information information Medical staff enters information about | External Record medical procedure a medical procedure Use Case and Domain Models 4) Create the Use Case Diagram based on the identified actors and use cases identified in Q3.[Part A] Q3: 10 to >7.5 Pts 7.5 to >6.26 Pts 6.26 to >5.0 Pts 5 to >0 Pts To what events must the Eastgate Excellent Good Satisfactory Unsatisfactory Health Co-Op Ltd Administrative Events, event types and Most events, event types Events, event types and Events, event types and System respond? List each event, resulting use cases have and resulting use cases resulting use cases have resulting use cases have not the type of event, and the resulting been completely and have been correctly been identified with some been identified or are use case. Be sure to consider all the correctly identified and identified. Good omissions or errors. Limited incorrect or very unclear. 10 pts use cases that would be needed to the CRUD approach description of the CRUD discussion of the CRUD There is no or an insufficient maintain the data in the system, described well. technique. technique. description of CRUD. thinking in terms of the CRUD technique. [Part A] Q4: 15 to >11.25 Pts 11.25 to >9.39 Pts 9.39 to >7.5 Pts 7.5 to >0 Pts Create the Use Case Diagram Excellent Good Satisfactory Unsatisfactory based on the identified actors and An exceptional level of The coverage of this A satisfactory Lacks clarity and a use cases identified in Q3. information was provided in requirement was above understanding of this clear understanding meeting this requirement. average, only minor issues and requirement has been of the assignment 15 pts Level of detail and clarity of errors detected. Level of detail demonstrated. Level of requirements. the Use Case Diagram is and clarity of the Use Case detail and clarity of the Use excellent. Diagram is good. Case Diagram is reasonable