Using the ERD in Figure 6.P1, transform the ProvNo attribute into an entity type (Provider) and a 1-M relationship (Treats). A provider has a unique provider number, a first name, a last name, a phone, a specialty, a hospital name in which the provider practices, an e-mail address, a certification, a pay grade, and a title. A provider is required for a visit. New providers do not have associated visits.

Now, expand the Visit entity type to record details about a visit. A visit detail includes a detail number, a detail charge, an optional provider number, and an associated item. The combination of the visit number and visit detail number is unique for a visit detail. An item includes a unique item number, an item description, an item price, and an item type. An item can be related to multiple visit details. New items may not be related to any visit details. A provider can be related to multiple visit details. Some providers may not be associated to any visit details. In addition, a provider can be related to multiple visits . The provider for a visit detail (usually a nurse or a lab technician) is typically different than the provider for the visit (usually a physician).

Then, transform VisitDetail into a strong entity type with VisitDetailNo as the primary key.

Then, add a history of item prices. Your solution should support the current price along with the two most recent prices. Include change dates for each item price.

Then, add a history of item prices. Your solution should support an unlimited number of prices and change dates.

Patient Visit PatNo PatFirstName PatLastName PatCity PatState PatZip PatHealth Plan VisitNo VisitD ate VisitPayMethod VisitCharge ProvNo .Attends Figure 6.P1: ERD for Problem 12 Patient Visit PatNo PatFirstName PatLastName PatCity PatState PatZip PatHealth Plan VisitNo VisitD ate VisitPayMethod VisitCharge ProvNo .Attends Figure 6.P1: ERD for Problem 12