I have started the first part (of overview/summary) thinking I will make the project about Mercy Hospital creating a healthcare database system (like an EHR). If it is possible to continue.

Prepare and submit a 1-2-page statement of work (SOW) to describe the need to create, design, and implement the database that you are proposing for your project. Within your SOW, the following minimum requirements must be met:

Minimum Requirements:

1.Overview/Executive Summary (10 points)

Provide a one-paragraph executive summary of your overall SOW. This section should not only effectively introduce your database concept but also highlight the key objectives, goals, and benefits. Recommend that you save this section for last to be completed once sections 2 through 7 below are done.

The purpose and goal of this project is to design and develop a healthcare database system for Mercy Hospital which will keep record and monitor patients medical history. This includes electronically consolidating stored data of medications, appointments, conditions, diagnoses, immunization dates, medical histories, patient demographics, lab and test results. The main objective is to improve quality of care and create a more effective means for providers and patients to access personal health data securely and efficiently. Benefits of a healthcare database system include access of all personal health records in one location at any given time. Increased communication, reduced medical errors and higher focus on patient care overall.

Mercy hospital wants to launch a database program which attracts patients to keeping informed with their medical data and acquired easy access to their history upon every health visit which will encourage patients to be up to date with their health. However, Mercy Hospital will need to acquire a way to develop a means to track, store, and maintain data securely.

2.Objectives of your database project (10 points)

Provide a comprehensive set of SMART objectives (https://www.mindtools.com/pages/article/smart-goals.htm) that outlines the scheduled implementation of each of your database project objectives from the submission of this SOW through your final project submission (all four project steps) at the end of week 11. This will require that you thoroughly examine and plan your database project using the Project Learning Demonstration under Hands-On Resources. A quality set of objectives will include not only the minimum requirements but also a critical analysis of second and third-order objectives that must be met in order to accomplish the primary database project objectives.

3.Project Scope (10 points)

As a complement to the objectives section, provide a one-paragraph statement along with a bullet-list of in-scope and out-of-scope work that outlines your database project scope which must answer two key questions:

What work is within the scope of my project and will be done?

What work is outside the scope of my project and will not be done?

4.Database Goals, Expectations, and Deliverables (10 points)

This section should be no more than one paragraph and it should address the end-state of your database project in terms of its usability and function as well as what items will and are required to be delivered when your final project is submitted.

5.Database Benefits (10 points)

Using your imagination and ability to critically think, this one-paragraph section should describe the potential benefits that the implementation and usage of your database will have on the business/organization/individual/etc. that ultimately uses it. Be creative and challenge yourself to find unique benefits beyond simply storing or querying/reporting on the underlying data.

6.Project Hardware and Software Tools (10 points)

Provide a comprehensive hardware and software inventory which will be a detailed description of all related hardware and software technologies to be used throughout your database project. This must include client-side and server-side technologies. The purpose of this section is two-fold: reproducibility and consistency. This will include but is not limited to: diagramming and design tools, development tools, office productivity, connectivity tools and access method, the DBMS system, client hardware, and server hardware.

a.

a.Diagramming Tool Identified

To further clarify, your SOW must accurately and completely identify the entity-relationship diagramming tool that you will use to design your entity-relationship diagram (ERD). This information must include not only the software name but also the version and platform (i.e. Windows, macOS, Linux).

b.

b.Database and Access Method Identified

In addition to the identification of your client (i.e. database design/development hardware and software) and server (database instance/platform), you must also completely identify the method or methods by which you will be accessing the server from the client. As with the previous objectives, you must not only identify the software and/or method itself but also the version (if applicable) and protocol.

7.SQL Usage and Style Guide (10 points)

Provide a detailed overview of the relevant SQL usage standards and styles that you will employ in your database project. This will include but is not limited to, SQL statement structure for readability, script format, comment usage, and object naming conventions. This section must also include a brief description of how data definition language (DDL) and data manipulation language (DML) statements will be used in your project.

8.Student-Defined Sections and Additional Content (10 points)

The purpose of this objective is for the evaluation and inclusion of your own unique and individual contributions, i.e. not one of the pre-defined minimum objectives, that further expand the depth of your SOW. Be creative and adventurous in your report by exploring additional content areas from domains such as database technology and project management.

9.One-to-Two Page Report Length (10 points)

At a minimum, your SOW should be at least one or two pages in length. A report that is less than one-page will not have satisfactorily met the minimum objectives listed above. Exceeding this minimum requirement is not only allowed but encouraged based on the depth of content and analysis provided.

10.Report Presentation (10 points)

In addition to the above objectives, your SOW will also be evaluated on the quality of presentation such as professional aesthetic, organization, logical flow, tonal consistency, and grammatical/spelling accuracy. For ease of identification, the sections of your SOW that address the qualitative goals above should be marked in some way with the goal itself.

Ensure that the following questions are addressed when completing the requirements above:

1.What is the business need and business problem that your database will solve?

2.What is the purpose of your database project?

3.What is the scope of your database project?

4.What will be achieved by implementing this database?

5.What benefits will the new database offer?

STEP 2

Project Step #2: Requirements Definition Document and Entity Relationship Diagram (ERD)

Prepare and submit your requirements definition document and entity relationship diagram (ERD) as two separate attachments to project step #2 assignment folder. Your requirements definition document must be submitted as a DOC/DOCX file and your ERD must be submitted using ER Assistant as an ERD file (or other supported diagramming format; see Project Learning Demonstration). Within your requirements definition document and ERD, the following minimum requirements must be met:

Requirements Definition Document Minimum Requirements:

1. Entity and Attribute Description (15 points)

For each entity, describe the entity itself as well as each of the attributes of the entity. You must also identify the primary key and any foreign keys. See the Project Learning Demonstration for examples of the entity and attribute descriptions. Note: if you are creating domain-specific attributes that are not common knowledge, you must provide a correspondingly more in-depth description of the entity or attribute.

1. Relationship and Cardinality Description (15 points)

For each relationship, describe the relationship itself, cardinality, business rules using the description format in the Project Learning Demonstration. To meet this requirement, you need only to describe the relationship that connects two entities one time.

1. Assumptions and Special Considerations (5 points)

This section should contain detailed descriptions of assumptions you are making about the project and any special considerations such as deviations from the lab project requirements.

Entity Relationship Diagram (ERD) Minimum Requirements:

1. Five Entities Minimum, Six Entities Maximum (10 points)

The purpose of the five-entity minimum, six-entity maximum is to establish a relatively small baseline for you to keep the scope of your database project constrained.

1. Five Attributes Minimum (10 points)

Each of your entities must have a minimum of five natural attributes which include the primary key. Foreign keys will not count towards the five-attribute minimum requirement.

1. Proper Relationships with Crow’s Feet Notation (20 points)

Each entity must be properly related to another using Crow’s Feet notation. Ensure that you properly denote the minimum cardinality and place the correct side of the relationship on the appropriate entity. There must be no many-to-many relationships; if these exist in your design they should be resolved before submitting project part 2.

1. Primary Key (5 points)

Each entity must have a primary key properly designated in your diagram that can be a natural, surrogate, or composite key.

1. Foreign Keys in Proper Locations (5 points)

All foreign keys should be placed on the appropriate side of the relationship according to your requirements definition documentation. Caveat: If using ER Assistant, be aware that foreign keys are derived implicitly from the relationship itself meaning that adding the foreign keys as actual attributes will result in diagram errors. Consider to add foreign key explicitly and get around the consistency check error by naming it using convention such as FK_parent_pk_col_name.

1. ERD Matches Requirements Definition (10 points)

Your diagram must accurately and completely translate the rules/requirements you previously outlined in the requirements definition document.

1. Proper Labels and Comments (5 points)

All relationships must be properly labeled with the verb or activity that they represent. From the Project Learning Demonstration, the EMPLOYEE to DEPARTMENT relationship would be labeled with ‘works’. Any other assumptions or special considerations should be placed on your ERD as comments.

part #2 Deliverables

1. Requirements Definition document in Word or PDF: LastName_FirstName_businessrules.[doc|pdf]
2. ERD in diagram specific format (i.e. .erd or .vsd) or Word/GIF/JPEG/PNG/PDF if using other diagramming tools: LastName_FirstName_ERD.[erd|vsd|pdf|doc|docx|gif|jpeg|png]

The lab project is cumulative meaning that you will submit the requirements definition document and ERD again during project step #4 with all errors corrected, content expanded, and formatting updated as required.

Learning Resources

See Project Learning Demonstration posted under Course Content/Hands-on Resources for step-by-step instructions.

PLEASE DONT ADD EXPLANATION WITH ANSWER