Reference no: EM133548716
Question: Create (E)ER diagrams for the following scenarios. (E)ER implies that superclass-subclass relationship may or may not be represented in the model and is dependent on the scenario. Make sure that you have read the mini-world descriptions carefully. Your diagrams should reflect all the entities, relationships, and attributes mentioned in the text descriptions. If you make any assumptions, please specify them in your answers. You may need to add a primary key if one hasn't already been specified in the mini-world description.
USE Crow's foot notation to create the ER diagram. But do not use a combination of both.
SimplyBlue is a health insurance company that wish to collect data in a database about their insurance claims. They keep track of their in-network physicians including their name, physician ID, and the hospital name. Physicians can treat one or more customers. On the other hand, customers can get treated by one or many physicians. As for the customers, SimplyBlue wishes to collect information such as their customer ID, name, address, and policy number. When a customer files a claim with respect to a treatment, it contains the customer ID, physician ID, date of service, medical codes, and total charges. Each customer can get treated by a same physician multiple times, so a separate treatmentRecordNo is also maintained in addition to customer ID and physician ID.