Category: Writing

Week 1: Discussion Question 2 – Applying Jean Watson’s Theory on Human Caring/Caring Science Core Principles to APN PracticeDiscussion Topic
Points: 20 | Due Date: Week 1, Day 5 & 7 | CLO: 5 | Grade Category: Discussions
Discussion Prompt
Jean Watson’s Theory of Human Caring/Caring Science is one theoretical framework used throughout the USU College of Nursing courses. The practice implication of Watson’s Human Caring Theory evolves our thinking and approaches to patient care from a mindset of carative (cure) to one of caritas (care). The core principles/practice are founded on a:
Practice of loving-kindness and equanimity
Authentic presence: enabling deep belief of other (patient, colleague, family, etc.)
Cultivation of one’s own spiritual practice toward wholeness of mind/body/spirit—beyond ego
“Being” the caring-healing environment
Allowing miracles (openness to the unexpected and inexplicable life events)
Some individuals are comfortable framing their practice with Watson while other prefer different theories or collection of theories. However, Watson is based on caring which a foundation of nursing. Anyone could use the core principles to guide decision making. Select one of the core principles and discuss ways you might be able to use in guiding your advanced practice nursing practices.
Resource:
Watson’s Caring Science Institute. (2018). Core concepts of Jean Watson’s Theory of Human Caring/Caring Science. Retrieved August 20, 2018 from https://www.watsoncaringscience.org/files/PDF/watsons-theory-of-human-caring-core-concepts-and-evolution-to-caritas-processes-handout.pdf
Jean Watson’s Philosphy of Nursing – http://currentnursing.com/nursing_theory/Watson.html
Watson, J. (2008). Nursing: The philosophy and science of caring (rev. ed.), Boulder: University Press of Colorado.
Expectations
Initial Post:
Due: Saturday, 11:59 pm PT
Length: A minimum of 250 words, not including references
Citations: At least one high-level scholarly reference in APA from within the last 5 years
Peer Responses:
Due: Monday, 11:59 pm PT
Number: A Minimum of 2 to Peer Posts, at least one on a different day than the main post
Length: A minimum of 150 words per post, not including references
Citations: At least one high-level scholarly reference in APA per post from within the last 5 years
Discussion: Respond to Posts in Your Own Thread

Enterprise Database Design
Key Terms
Week 1 Key Terms:
Data – Raw facts that have little meaning unless organized and context provided.
Information – Data that have been processed to provide context to increase the
knowledge of the person who uses it.
Database – An organized collection of logically related data.
Database management system – A software system that is used to create, maintain,
and provide controlled access to user databases.
Data governance – The management of the availability, usability, integrity, and security
of the data created and used in an enterprise. A robust data governance program
includes a governing, a defined set of procedures, and a plan to execute those
procedures.
IT governance – The management of IT projects, IT systems and IT strategy with the
organization’s business strategy, ensuring that companies stay on track to achieve their
strategies and goals.
Week 2 Key Terms:
Conceptual data model – A detailed, technology-independent specification of the
overall structure of organizational data. The conceptual data model is typically an Entity
Relationship Diagram showing all entities and relationships between entities.
Logical data model – The representation of data for a data management system. In
the case of a relational data model, elements include tables, columns, rows, primary
and foreign keys, as well as constraints.
Physical data model – A set of specifications that detail how data from a logical data
models are stored in a computer’s secondary memory for a specific database
management system. There is one physical data model for each logical data model.
Entity – A person, place, object, event, or concept in the user environment about which
the organization wishes to maintain data.
Associative entity – An entity that associates the instances of one or more entity and
contains attributes that are peculiar to the relationship between those entity instances.
Weak entity – An entity whose existence depends on some other entity.
1 of 4
Enterprise Database Design
Key Terms
Week 2 Key Terms Continued:
Entity-relationship model – A logical representation of the data for an organization or
for the business requirements.
Relationship type – A meaningful association between entities.
Attribute – A property or characteristic of an entity type that is of interest to the
organization.
Identifier – An attribute (or combination of attributes) that uniquely identifies individual
instances of an entity type.
Constraint – A rule that cannot be violated by database users.
Cardinality constraint – Specifies the number of instances of one entity that can (or
must) be associated with each instance of another entity.
Candidate key – A “candidate to be the primary identifier” of an entity.
Primary key – A primary key is a candidate key that has been selected as the identifier
for an entity type. The primary key uniquely identifies a row; cannot contain null values.
A primary key can be composed of multiple columns.
Foreign key – Column(s) whose values match the values in a candidate key of another
table.
Week 3 Key Terms:
Normalization – The process of decomposing relations with anomalies to produce
smaller, well-structured relations.
Determinant – The attribute on the left-hand side of the arrow in a functional
dependency.
Functional dependency – A constraint between two attributes or two sets of attributes.
Transitive dependency – A functional dependency between two (or more) non-key
attributes.
Normal form – A state of a relation that results from applying simple rules regarding
functional dependencies (or relationships between attributes) to that relation.
Partial functional dependency – A functional dependency in which one or more nonkey
attributes (such as Name) are functionally dependent on part (but not all) of the
primary key.
2 of 4
Enterprise Database Design
Key Terms
Week 3 Key Terms Continued:
1NF – No multi-valued attributes; no repeating groups that have assumed values rather
than real values; every attribute value is atomic; all relations are in 1NF.
2NF – Every non-key column depends on a entire primary key, not part of a key; no
partial functional dependencies; every relationship/table is in both 2NF and 1NF.
3NF – Every non-key column depends only on a key not on non-key columns; no
transitive dependencies; every relationship/table is in 3NF, 2NF and 1NF.
Week 4 Key Terms:
Conceptual data model – A detailed, technology-independent specification of the
overall structure of organizational data.
Logical data model – The representation of data for a particular data management
technology. In the case of a relational data model, elements include tables, columns,
rows, primary and foreign keys, as well as constraints.
Physical data model – A set of specifications that detail how data from a logical data
models is stored in a computer’s secondary memory for a specific database
management system. There is one physical data model for each logical data model.
Database – An organized collection of logically related data.
Database management system – A software system that is used to create, maintain,
and provide controlled access to user databases.
Structured Query Language (SQL) – This is the language used to retrieve and
manage data within relational database management systems. The language includes
groupings of the language such as DDL, DCL, and DML.
Data Definition Language (DDL) – These commands are used to create, alter, and
drop tables and other database structures. The commands include the CREATE,
ALTER, DROP, and TRUNCATE commands.
Data Manipulation Language (DML) – These commands are used to manipulate the
data within the tables. The commands include INSERT, UPDATE, DELETE, and
MERGE.
Data Control Language (DCL) – These commands are used to authorize users to
access various data and data structures. These commands use keywords GRANT,
DENY, and REVOKE.
3 of 4
Enterprise Database Design
Key Terms
Week 5 Key Terms:
Database management system – A software system that is used to create, maintain,
and provide controlled access to user databases.
Structured Query Language (SQL) – This is the language used to retrieve and
manage data within relational database management systems. The language includes
groupings of the language such as DDL, DCL, and DML.
Data Definition Language (DDL) – These commands are used to create, alter, and
drop tables and other database structures. The commands include the CREATE,
ALTER, DROP, and TRUNCATE commands.
Data Manipulation Language (DML) – These commands are used to manipulate the
data within the tables. The commands include INSERT, UPDATE, DELETE, and
MERGE.
Data Control Language (DCL) – These commands are used to authorize users to
access various data and data structures. These commands use keywords GRANT,
DENY, and REVOKE.
Join – Return rows when there is at least one match in both tables
Left Outer Join – Returns all rows from the left table, even if there are no matches in
the right table
Right Outer Join – Returns all rows from the right table, even if there are no matches in
the left table
Full Outer Join – Returns rows from both tables, even when the row is not matched.
In – Operates on any records in the containing command where the specified
expression appears in the subquery results.
Exists – Operates on any records in the containing command where the subquery result
has at least one row.
4 of 4
Attachments:
3081894_1_USW1-ITEC-6145-keyTerms.pdf
3081894_2_ITEC6140DatabaseTable-DT03.pdf
3081894_3_ITEC6140DatabaseTable-DT02.pdf
3081894_4_ITEC6140DatabaseTable-DT01.pdf