ENTITIES RELATIONSHIP DIAGRAM

SCENARIO You are a nurse informatics specialist at a regional health center in the Midwest where the emergency department (ED) has recently experienced an alarming number of asthma-related symptom complaints from school-age children. The ED doctors noted a pattern in these complaints that indicated asthma symptoms were not being well managed. To address this community-wide issue, an interprofessional team of ED doctors, pediatricians, nurses, and health educators was called to brainstorm ideas. The team is currently developing a symptom management intervention program for parents of children with asthma. However, in order to measure the effectiveness of their work, the team decided to collect and analyze data before they put their program in place. Later they plan to compare this initial data to additional data they will collect after implementing their program. To collect their initial data, the team created a paper-based data-collection form and distributed it to all parents of children attending schools in the county. The form was designed to capture information on personal identifying factors, demographics, relevant medical history, and asthma symptoms. The team received more than 500 responses and quickly realized they did not have the knowledge, skills, or abilities to manage the data for this project. The team then came to you for help with designing a system to collect, manage, and analyze survey data. They handed you the data-collection survey form and indicated that they need the database management system as soon as possible. You reviewed the form and created the attached “Code Sheet for ERD” with all the data elements on the form. You then began the process of clustering the data elements into tables. You determined that there will be one parent table that will contain personal identifying information and demographics. You have also determined that there will be one child table that will contain repeated surveys—pre- and post-intervention. In addition, you noted that the system will need three lookup tables for drop-down boxes. By creating the correct relationship between the parent and child tables, it will be possible to conduct statistical analyses that will determine the effectiveness of the educational program by comparing pre-intervention survey responses to post-intervention responses. After clustering data elements, and determining relationships, it is time to create a logical data model of the database. To create the data model, you will use Visio to generate an ERD. You will present this model to the team to make sure the system will include all the information needed and that the system will function efficiently. You will then begin the process of building an Access DBMS using the information in Unit 4 of your course. REQUIREMENTS Your submission must be your original work. No more than a combined total of 30% of the submission and no more than a 10% match to any one individual source can be directly quoted or closely paraphrased from sources, even if cited correctly. An originality report is provided when you submit your task that can be used as a guide. You must use the rubric to direct the creation of your submission because it provides detailed criteria that will be used to evaluate your work. Each requirement below may be evaluated by more than one rubric aspect. The rubric aspect titles may contain hyperlinks to relevant portions of the course. For this assessment you will create an ERD (entities relationship diagram) in Microsoft Visio, using the attached “Code Sheet for ERD.” Then you will use Microsoft Access to create a database management system (DBMS) using information from your completed ERD and the instructions in Unit 4 of your course. You will not submit the database, just a screenshot of your work. Finally, you will write a paper reflecting on your experiences. A. Create a logical ERD using appropriate entities and data elements by doing the following: 1. Create one parent table that incorporates the following points: • correct labels • an established primary key • data elements, related to the entity, entered in the attribute cells 2. Create one child table that incorporates the following points: • correct labels • correctly identified primary and foreign keys • data elements, related to the entity, entered in the attribute cells