Create a logical data model documented with an ERD using the crows foot format. Be sure that each entity has the entity name at the top of the box, the primary key attribute or attributes in the middle of the box, and the non-key attributes in the bottom of the box. Lines should separate each part of the entity box. Follow these instructions about each ERD:

The ERD must not have any many-to-many (m:n) relationships. All attributes must be placed within an entity.

Each entity must have a primary key defined. A primary key can consist of one or more attributes.

Each relationship must have a foreign key. Denote the foreign key(s) with the notation (FK) on the ERD. Remember that in a one-to-many relationship, the foreign key is placed in the entity that is on the many side of the relationship.

Each relationship must include both a maximum and minimum cardinality for both sides of the relationship.

Each relationship should have a verb or verb phrase to describe it.

You do not have to differentiate between an identifying or non-identifying relationship.

Question: Application Scenario The purpose of this database is to store summarized data about hospital visits in order to do data analysis for a hospital. Although the charges and reimbursement data are accurate, all the rest of the data is made-up to protect the privacy of patients. Both the patient and doctors names in this dataset are created; they are not real. The sample data is provided for you in an Excel workbook called HospitalVisitData. Each visit to the hospital has its own primary key (HospitalStayID). A patient may visit the hospital more than once. Each hospital visit by a patient will have the following data: patientID, total charges, total charges reimbursed, and the length of stay in days. A hospital stay is related to one and only one patient. For each patient, we store the patientID (which is a unique value for each patient), and the patients first and last names. Each hospital stay may be related to zero or many procedures. A given procedure may be related to many different hospital stays. For each procedure, the hospital keeps track of a standard procedure code (primary key) and a standard long description. A procedure is identified by a procedure code. These procedure codes are standardized by the healthcare industry and are known as CPT codes. These codes are the basis for Medicare billing and standardize the billing for services performed on Medicare patients across the United States. During a hospital visit, a patient may or may not have procedures done on them by a doctor. Data stored about a doctor includes a unique doctorID, first name, and last name. A procedure for a given hospital stay is performed by one and only one doctor. Sample data for this database is available in the HospitalVisitData Excel workbook.. After drawing the ERD for this application scenario, create each table required to implement the database in SQL Server. Copy the CREATE TABLE statements you write to the Word document