draw an ERD containing the patient, physician, and visit entity types. a patient can see multiple physicians but only one physician on any one given visit. choose appropriate names for the relationships. define minimum cardinalities so that patients and physicians are required on a visit, while patients don't have to be assigned to physicians(and vice cersa). for the patient entity type, add attributes PatNo, PatFirstName, PatLastName, PatStreet, PatCity, PatState,PatZip, and PatHealthPlan. for the physician entity type, add attributes PhyNo, PhyFirstName, PhyLastName, PhySpecialty, PhyPhone, PhyEmail, PhyHospital, and PhyCertification. for the visit entity type, add attributes for the VisitNo, VisitDate, VisitPayMethod(cash, check or credit card), and visitCharge. next add nurse, item, and visitdetail entity types. on each visit multiple details are recorded in visitdetail by one nurse. visitdetail has a 1-M relationship from visit to visitDetail. choose appropriate names for the relationships . define minimum cardinalities so that a nurse can be assigned on a visit detail, an item is required for a visit detail. for the item entity type, add attributes ItemNo, ItemDesc, ItemPrice, and ItemType. for the nurse entity type, add attributes NurseNo, NurseFirstName, NurseLastName, NurseTitle, NursePhone, NurseSpecialty, and NursePayGrade. for the visitDetail entity type, add attributes for the detailNo and detailCharge. make sure you choose appropriate data types for the attributes based on your common knowledge. select suitable primary keys and foreign key. clearly label weak entities, and identifying and non-identifying relationships.