Presentation is loading. Please wait.

Presentation is loading. Please wait.

Entity Relationship Diagram Farrokh Alemi Ph.D. Francesco Loaiza, Ph.D. J.D. Vikas Arya.

Similar presentations


Presentation on theme: "Entity Relationship Diagram Farrokh Alemi Ph.D. Francesco Loaiza, Ph.D. J.D. Vikas Arya."— Presentation transcript:

1 Entity Relationship Diagram Farrokh Alemi Ph.D. Francesco Loaiza, Ph.D. J.D. Vikas Arya

2 2 Objective How to construct an Entity Relationship (ER) Diagram How to construct an Entity Relationship (ER) Diagram –An example A dialogue between a student and the instructor

3 I Don't Understand! I Don't Understand! Can you give me an example?

4 Purpose of ER Diagrams To describe the structure of the database

5 ER diagram? What is it?

6 Definition of ER Diagrams ER diagram is a list of entities and their relationship to each other

7 Definition of Entity Anything about which we want to keep persistent data

8 8 From Logical to Physical EntityAttributesValuesTableFieldsData

9 Jargon? Why is it important?

10 Design of Large Databases ER diagrams make it possible to have large databases

11 Logically missing data? What do you mean?

12 12 Logically Missing Data When users have to leave a field as blank because it is not appropriate for the record –For example, if the patient's visit was about asthma, and we record data on hypertension

13 Duplication wastes effort

14 14 Redundant Data In every visit you would need all information about the patient (e.g. contact information, insurance information, etc.) In every visit you would need all information about the patient (e.g. contact information, insurance information, etc.) This leads to redundant patient data on each record

15 Multiple Tables Reduce Inefficiencies ER diagram leads to specification of multiple tables

16 Recognizing Entities Use case and description of database functions

17 17 Electronic Medical Record An EMR is used by a provider of care to record information about the patient's visit so that the treatment can be coordinated over time with other providers. An EMR is used by a provider of care to record information about the patient's visit so that the treatment can be coordinated over time with other providers. It is also used to bill the patient about treatment they have received."

18 Looking for Entities Examine statements about uses of EMR database

19 19 I See Two Entities An EMR is used by a provider of care to record information about the patient's visit so that the treatment can be coordinated over time with other providers. An EMR is used by a provider of care to record information about the patient's visit so that the treatment can be coordinated over time with other providers. It is also used to bill the patient about treatment they have received."

20 20 More Entities An EMR is used by a provider of care to record information about the patient's visit so that the treatment can be coordinated over time with other providers. An EMR is used by a provider of care to record information about the patient's visit so that the treatment can be coordinated over time with other providers. It is also used to bill the patient about treatment they have received."

21 21 Diagnosis Patient Treatment Diagnosis is about Patients? Other facts

22 Depends on More Than Patients No. Diagnosis is not a stable fact about the patient. It shows the condition of the patient at a point in time, during the visit

23 Treatment? Is treatment a fact about the patient?

24 24 Treatment Entity Code Charge Description Treatment Risk

25 25 Primary Key All the facts in the table are about the primary key & no other field All facts in the table should be unique for a given primary key.

26 Key Organizing Concept Primary key is what tables are organized around

27 27 Facts Belong to Primary Keys If a fact can belong to the primary key and nothing else, then it belongs to the entity If a fact can belong to the primary key and nothing else, then it belongs to the entity Otherwise it belongs to a different entity Consider address Consider address Consider diagnosis Consider diagnosis

28 Not Black & White Address does not belong to the patient either as it changes over time

29 29 Design Choices Number of Tables & Entities For our example

30 Art & Science Do’s and Don’ts

31 Patient Attributes? What fields are needed?

32 Social Security Number Avoid it to improve privacy

33 33 Primary Keys for Patient Entity Combination of fields Auto-number

34 34 Patient Entity Attributes Contact information Demographic data Address

35 Atomic Facts not Collections of Facts Address is a collection of facts

36 36 Patient Attributes Revised Street Date of Birth First name Patient Gende r Last name Middle initials Race Insurance number Insurance company Zip Street number city State

37 Provider table? What attributes should be included in the Provider table?

38 38 Provider Attributes Street Date of Birth First name Providers Title Last name Middle initials Year of graduation Board certification Telephone Zip Street number city State Email Employee ID

39 Treatment Entity? What attributes should be included?

40 40 Treatment Attributes Code Cost Description Treatment Warning Typical medication

41 41 Visit Table Many records Few fields

42 42 Visit Attributes Provider ID Patient ID Diagnosis Visit ID Date Treatment code

43 43 Foreign Keys Primary keys of another table Included to link to other tables

44 Components of ER Diagram ER Diagram Shows each entity (their attributes) and the relationship between the entities

45 Setting Relationships In Access you can do this by creating the tables and then connecting the tables to each other

46 What If What if information in one table is inadvertently deleted. Then we loose the meaning of information in other tables. What if information in one table is inadvertently deleted. Then we loose the meaning of information in other tables.

47 Inferential Integrity Cascaded deletion of all related records

48 How? How do you set inferential integrity in Access?

49 Cascaded Updates Updating one table will lead to the change for all other related tables

50 Types of Joins Matching to missing information

51 Join Examples? Give me an example of when you want to have this type of joins.

52 52 Non-clinical Providers Know if there are providers not taking care of any patients. Know if there are providers not taking care of any patients. If we stay with our match of foreign and primary key all cases with no match will be eliminated and we will not be able to see if there is a provider with no patient. If we stay with our match of foreign and primary key all cases with no match will be eliminated and we will not be able to see if there is a provider with no patient.

53 Relationships in Words? Is there a way of putting words to the relationship between two tables

54 54 Relationships in Words The words of course are implied in the field names. The words of course are implied in the field names. –If the foreign key is ID of the son, then it implies that it links the father to the son. –If the foreign key is ID of the son, then it implies that it links the father to the son. Some ER diagrams allow the specification of the relationships in words. Some ER diagrams allow the specification of the relationships in words.

55 55 One to One Joins A one to one relationship requires a record for each item in the other table. A one to one relationship requires a record for each item in the other table. –For example, a word and its meaning in a dictionary have a one to one relationship."

56 56 One to Many Joins Yes, a one to many relationship allows one record to have multiple records in another table linked to it. Yes, a one to many relationship allows one record to have multiple records in another table linked to it. –For example, the patient record may have multiple records in the visit table." –For example, the patient record may have multiple records in the visit table."

57 One Patient Many Visits Yes that makes sense

58 58 Many to Many Joins Suppose we want to allow a patient to live at two different addresses and two different patients (mother and a child) to live at same address. Suppose we want to allow a patient to live at two different addresses and two different patients (mother and a child) to live at same address. Problems: Primary keys need to be unique. Problems: Primary keys need to be unique. One way to solve this problem is to introduce a junction table One way to solve this problem is to introduce a junction table

59 Example of Junctions? Could you layout the example in more detail?

60 60 Patient & Address Junction Table

61 Advantage of Junctions We can have primary keys in patient and address table that are unique but have them listed in multiple ways in the junction table We can have primary keys in patient and address table that are unique but have them listed in multiple ways in the junction table

62 62 Patient & Patient Junction IDParentChildRelationship 1234213Mother to 2213215Mother to 3200215Father of

63 Allows Self Relationships This is a clever way of keeping information about primary keys in same table

64 64 Take Home Lessons Definitions, including terms such as entity, attribute and values. Definitions, including terms such as entity, attribute and values. How entities can be identified. How entities can be identified. Specification of attributes Relationships among tables using foreign and primary keys. Relationships among tables using foreign and primary keys. Types of relationships and inferential integrity. Types of relationships and inferential integrity. Junction table can be used to represent many to many relations and relationships between the table and itself

65 65 Take Home Lessons Definitions, including terms such as entity, attribute and values. Definitions, including terms such as entity, attribute and values. How entities can be identified. How entities can be identified. Specification of attributes Relationships among tables using foreign and primary keys. Relationships among tables using foreign and primary keys. Types of relationships and inferential integrity. Types of relationships and inferential integrity. Junction table can be used to represent many to many relations and relationships between the table and itself

66 66 Take Home Lessons Definitions, including terms such as entity, attribute and values. Definitions, including terms such as entity, attribute and values. How entities can be identified. How entities can be identified. Specification of attributes Relationships among tables using foreign and primary keys. Relationships among tables using foreign and primary keys. Types of relationships and inferential integrity. Types of relationships and inferential integrity. Junction table can be used to represent many to many relations and relationships between the table and itself

67 67 Take Home Lessons Definitions, including terms such as entity, attribute and values. Definitions, including terms such as entity, attribute and values. How entities can be identified. How entities can be identified. Specification of attributes Relationships among tables using foreign and primary keys. Relationships among tables using foreign and primary keys. Types of relationships and inferential integrity. Types of relationships and inferential integrity. Junction table can be used to represent many to many relations and relationships between the table and itself

68 68 Take Home Lessons Definitions, including terms such as entity, attribute and values. Definitions, including terms such as entity, attribute and values. How entities can be identified. How entities can be identified. Specification of attributes Relationships among tables using foreign and primary keys. Relationships among tables using foreign and primary keys. Types of relationships and inferential integrity. Types of relationships and inferential integrity. Junction table can be used to represent many to many relations and relationships between the table and itself

69 69 Take Home Lessons Definitions, including terms such as entity, attribute and values. Definitions, including terms such as entity, attribute and values. How entities can be identified. How entities can be identified. Specification of attributes Relationships among tables using foreign and primary keys. Relationships among tables using foreign and primary keys. Types of relationships and inferential integrity. Types of relationships and inferential integrity. Junction table can be used to represent many to many relations and relationships between the table and itself


Download ppt "Entity Relationship Diagram Farrokh Alemi Ph.D. Francesco Loaiza, Ph.D. J.D. Vikas Arya."

Similar presentations


Ads by Google