(Database Design Normalization: functional dependency)

Patient(patient_number, pat_name, pat_phone, insurance_code, ins_company, ins_class, primary_physician_id, prim_phys_name, prim_phys_phone, visit_time_date, visit_physician_id, diagnosis, treatment, fee)

(1). Design the schema of relational tables for storing these patient-records, all tables in BCNF. Underline primary keys and show foreign keys using arrows.

(2). If patients' insurance data and primary physician data were changed very infrequently. Now, compromise the relational schema design accordingly so that the above mentioned queries run faster while you still do not have to store patient records more than once. Show your modified schema diagram.

patient-number-) pat-name, pat-phone, insurance-code, ins-company, ins-class, primary physician id, prim phys _name, prim phys phone insurance code ins-company, ins-class . * primary_physician_id -> prim phys_name, prim phys_phone patient _number, visit_time_date) -> visit physician_id, diagnosis, treatment, fee