You design and develop a database for the hospital to maintain the records of various departments, and doctors in the hospital. It should be able maintain records of the regular patients, patients admitted in the hospital, the checkup of patients administered by the doctors, and the patients that have been operated from the hospital. Requirements of a database to stores information about Hospital Management System are as follows: . . For each doctor, the database contains id number which is unique to identify them, name, salary, a phone number and specialties. A doctor may have multiple specialties. Departments store the information of all the departments including a unique department name, a department location and facility. A doctor should work in a department. When any patient arrives in the hospital for the first time checkup, a patient record is created including a patient number, a patient name, age, phone number, and address. The patient number will be uses for identifying a patient. In addition, a doctor will be assigned as a check-up doctor (i.e., primary doctor). There are two types of patient: (i) admitted patient including date of admitted, room# and condition, and (ii) regular patient including date of visit, prescription and payment method. A patient should be either admitted or regular patient. When doctors perform the operations on patient(s), type of operation, condition, and date of operation should be stored for each operation. Please create an Extended Entity Relationship diagram that captures this information about Hospital Management System. Be certain to indicate identifiers and cardinality constraints. Also, you should indicate disjoint/complete constraints of super-sub classes, i.e., EER model. Answer) ytpe cond date id name salary operations number name age M N phone phone PATIENTS specials DOCTORS N address N check-up works-in name DEPARTMENTS ADMITTED PATIENTS REGULAR PATIENTS location facility date Room cond dateVisit prescri ption payment Map the above Hospital Management System EER diagram (in Q21) into a relational schema diagram. For Super-sub classes entity, please use Option 1, i.e., one table for each class