Case Description: A small medical clinic needs a relational database for its medical practice. The clinic currently keeps its patient visits and invoices data in a spreadsheet. Since it is hard to maintain data integrity in a spreadsheet, and also inconvenient and not practical to perform data updates and query processing in a spreadsheet using a query language such as SQL$,$ the clinic now wants to migrate the data to a relational database. The clinic spreadsheet currently has the following columns: First name, last name and phone numbers of doctors and patients, patient visit date and time, and invoice date and invoice amount. Business Rules: The clinic has the following business rules and requirements: a$.$ Although a patient can visit many doctors in the clinic and a doctor can see many patients, each patient visit is only between one patient and one doctor. b$.$ After a patient's visit with a doctor, an invoice is generate for the patient.. The Task:As a junior DBA, your task is to design a relational database schema $($i$.$e$.,$ a set of tables and their columns$)$ for the clinic data described above. Please be sure that all tables in the schema are normalized to third normal form $(3$NF$).$ Also, every table in the schema should have a primary key add a new column for this purpose if the current list of columns does not have an appropriate primary key column. Tables should have foreign key columns as needed. What to submit: Write the list of tables in the database schema. Each table in the schema should be listed using the following format: Table $1$ Name $($ Primary Key Column$/$s Underlined, Non$-$key Column $1,$ Non$-$key Column $2,..)$Table $2$ Name $($ Primary Key Column$/$s Underlined, Non$-$key Column $1,$ Non$-$key Column $2,..)$Table $....$ A Schema Example: PRODUCTS $($Product$\_$Code, Product$\_$Name, Price$-$Per$-$Unit, SupplierID$)$SUPPLIERS $($SupplierID$,$ Supplier$\_$Name, Supplier$\_$Phone$)$