Introduction Database Creation

Question 1a:

Patient Name: Dolan, Mark

Patient Number: 4238

Patient Address: 818 River Run

Item Code: 275 Item Description: Radiology Amount: 150

Item Code: 200 Item Description: Room Semi-Priv Amount: 1600

Item Code: 700 Item Description: EEG Test Amount: 200

Question 1b:

No, the enterprise model pictured does not contain the data needed to generate a bill. It does however show some of the inner workings of a hospital. There is no accounting or billing department listed.

Question 2:

1. Entity type: A collection of entities that share common properties or characteristics.

a. Entity Type = City.

2. Entity instance: Is a single occurrence of an entity type.

a. If entity Type = City, then Cedar Rapids is an entity instance.

3. Attribute: A property or characteristic of an entity type that is of interest to the organization.

a. Customer names

4. Relationship type: A meaningful association between (or among) entity types.

a. Customer  PURCHASED  Product = Purchased is the relationship type

5. Identifier: An attribute (or combination of attributes) that uniquely identifies individual instances of an entity type.

a. If entity type = Customer, then Customer ID would be an identifier.

6. Associative entity: An entity type that associates the instances of one or more entity types and contains attributes that are peculiar to the relationship between those entity instances.

a. Student completes degree plan and is issued a diploma = diploma is associative entity

7. Cardinality constraint: Specifies the number of instances of one entity that can (or must) be associated with each instance of another entity.

a. 1 book is stocked as 0 (min) or many (max) hardcover editions

8. Weak entity: An entity type whose existence depends on some other entity type.

a. Parent (strong entity)/Child (weak entity)

9. Identifying relationship: Is the relationship between a weak entity type and its owner.

a. Parent (strong...