University of Texas Human Mod 2 Technology Interface Application Paper This week you will identify, research, and discuss human-technology interface/intera

University of Texas Human Mod 2 Technology Interface Application Paper This week you will identify, research, and discuss human-technology interface/interactions related to nursing informatics. Information presented in the written assignment will also focus on the application to your role in nursing administration or nursing education.

Instructions:

Review the grading rubric and instructions below BEFORE continuing with the assignment.
Based on your observations, submit a written paper based on the following headings:
Definition

Provide the definition of human-technology interface based on the literature and give 2 examples, based on your observations. Include references.

Human-Technology Interface Issue

Identify, analyze, and describe 1 human-technology interface/interaction issue (not mentioned in the text) and describe your proposed solution. Be specific. Include references.

Human-Technology Interface Working Well

Identify, analyze, and describe 1 human-technology interface/interaction (not mentioned in the text) that you think is working well as designed. Be specific. Include references.

Impact to Role

Describe how human-technology interfaces can impact your role as a nurse administrator or nurse educator. Be specific and provide an example. Include references.

Review the literature and cite a minimum of 3 peer-reviewed articles. Additional references may include your textbook and websites from the list of Informatics Websites provided in Course References.
Submit a written paper and include a cover page and reference page (Use APA format).
Maximum 1000 words not including cover page and reference page. Refer to the rubric for additional information.

Textbook

McGonigle, D. & Mastrian, K.G. (2018). Nursing informatics and the foundation of knowledge. (4th Ed.). Burlington, MA: Jones & Bartlett Learning. Module 2: Human-Technology Interface Grading Rubric
Module 2: Human-Technology Interface Grading Rubric
Criteria
This criterion is linked to a
Learning
OutcomeDefinition (20 pts)
1. Provide the definition of
human-technology interface
based on the literature. 2.
Provide examples based on
observations
This criterion is linked to a
Learning OutcomeHumanTechnology Interface Issue
(20 pts) Identify, analyze,
and describe 1 humantechnology
interface/interaction issue
(not mentioned in the text)
and describe your possible
solution. Be specific.
Include references
Ratings
20.0 to >17.0 pts
Accomplished
• Clearly describes the
definition • References
cited • Provided 2
examples based on
observations
20.0 to >17.0 pts
Accomplished
• Presents an insightful and
thorough analysis and
description of the humantechnology interface issue •
Uses problem-solving and
critical thinking skills and
describes a possible solution •
Excellent research into the
issues with clearly
documented references
relevant to the topic
17.0 to >15.0 pts
Acceptable
• Definition partially
provided or not clear •
References provided •
Provided 2 examples
based on observation
17.0 to >15.0 pts
Proficient
• Presents a thorough
analysis and description
of the human-technology
interface issue • Uses
problem-solving and
critical thinking skills and
partially describes a
possible solution • Good
research into the issue
with documented
relevance to the topic
15.0 to >13.0 pts
Acceptable
•Minimal information
provided for the definition
•References not included
•Provided 1 example based
on observations
15.0 to >13.0 pts
Acceptable
• Presents a superficial or
incomplete analysis and
description of the humantechnology interface issue
• Uses limited problemsolving and critical
thinking skills without
identifying a possible
solution • Limited
research and documented
relevance to the topic
13
N
•D
st
no
ex
Module 2: Human-Technology Interface Grading Rubric
Criteria
This criterion is linked to a
Learning OutcomeHumanTechnology Interface
Working Well (20 pts)
Identify, analyze, and
describe 1 humantechnology
interface/interaction
working well as designed
(not mentioned in the text)
and describe your possible
solution. Be specific.Include
references
This criterion is linked to a
Learning OutcomeImpact to
Role (20 pts) Describe how
human-technology
interfaces can impact your
role as a nurse administrator
or nurse educator. Be
specific and provide an
example. Include references.
Ratings
20.0 to >17.0 pts
Accomplished
• Presents an insightful and
thorough analysis and
description of the humantechnology interface working
well as designed • Uses
problem-solving and critical
thinking skills and describes
reason for ideal design •
Excellent research into the
topic with clearly
documented references
relevant to the topic
17.0 to >15.0 pts
Proficient
• Presents a thorough
analysis and description
of the human-technology
interface working well as
designed • Uses problemsolving and critical
thinking skills and
partially describes reason
for ideal design • Good
research into the issue
with documented
relevance to the topic
15.0 to >13.0 pts
Acceptable
• Presents a superficial or
incomplete analysis and
description of the humantechnology interface
working well as designed
• Uses limited problemsolving and critical
thinking skills without
identifying reason for
ideal design • Limited
research and documented
relevance to the topic
20.0 to >17.0 pts
Accomplished
• Clearly describes in detail,
how human-technology
interfaces your role •
Presents a detailed, insightful
and thorough explanation
and example • Supported by
references
17.0 to >15.0 pts
Proficient
• Human-technology
interface impact to your
role is not clearly defined
• Explanation and
example present but not
clearly presented •
Supported by references
15.0 to >13.0 pts
Acceptable
• Human-technology
interface impact to your
role is vague or
incomplete •
Explanation and
example vaguely
presented • Missing
references
1
N
•
p
H
in
w
D
p
c
s
r
13.
No
•H
inte
you
Exp
exa
Mis
Module 2: Human-Technology Interface Grading Rubric
Criteria
Ratings
This criterion is linked to a
Learning OutcomeLinks to
Literature (10 pts) • Use 3
peer-reviewed articles
within the last 5 years •
Textbook and informatics
websites, optional
10.0 to >8.0 pts
Accomplished
• At least 3 peer-reviewed
articles are cited
This criterion is linked to a
Learning OutcomeWriting
and APA including: (10 pts)
1. Writing is clear,
objective, formal, and
professional 2. Correct
grammar, spelling, and
punctuation 3. Use APA
format for written
assignment 4. Cover page
according to APA format 5.
Reference page according to
APA format 6. Maximum
1000 words (not including
cover page and reference
page)
10.0 to >8.0 pts
Accomplished
• Complete formatting and
writing • APA with 1 or fewer
errors.
Total Points: 100.0
PreviousNext
8.0 to >6.0 pts
Acceptable
• At least 2 peer-reviewed
articles are cited
8.0 to >6.0 pts
Acceptable
• 2-3 formatting,
writing or APA errors
6.0 to >4.0 pts
Proficient
• At least 1 peerreviewed article is cited
6.0 to >4.0 pts
Proficient
• 4-5 formatting,
writing or APA
errors
4.0 t
Not
• Pee
artic
4.0 to
Not A
• More
forma
APA e
N5308 Nursing Informatics
Script
Module 2 – Overview
Slide 1 – Module 2 Overview
Hello and Welcome to Module 2! I hope you had a great week!
The topics to be covered this week are system development, human-technology interface, and
terminology in nursing.
I will introduce the objectives and give an overview of the content. Assignments for this week
include the discussion board and a written assignment. As a reminder, be sure to check the
Guidelines for Substantive Posts for the Discussion Board and the instructions and grading
rubric for the assignment. Be sure to check the To Do List in Blackboard for items to be
completed this week.
Slide 2 – Module 2 Objectives
Let’s review the objectives for this week. We will explore an overview of the system
development life cycle, evaluate selected approaches to the System Development Life Cycle,
explore Human-Technology interfacess, and review terminology in nursing.
In Blackboard, in module 2, you will find these module objectives and the associated course
outcomes. There is also a topic outline for your reference.
Slide 3 – System Development Life Cycle-Overview
Let us now transition to the System Development Life Cycle also referred to as SDLC. What is
the System Development Life Cycle? It is a method or process to deliver efficient and effective
information systems to fit with the strategic business plan of an organization. For example, a
hospital needs to update the electronic health record system for a new service line or a hospital
is thinking about implementing brand new IV pumps across the organization. So what is the
best method to complete these projects?
The system design process is basically 5 steps or phases. To help explain this concept, the
System Development Life Cycle can be compared to the nursing process. This was a great ah-ha
moment for me when I started in nursing informatics.
Assessment relates to the requirements for the system. These are the elements of the system
such as a place to document vital signs, a flowsheet for the assessment, or the staffing schedule
for assignments. These elements are the deliverables for the project. Also included in the
requirements is the budget and timeframe for the project. The cost-benefit analysis is a key first
piece in planning the budget. Will implementing this new system or upgrading an existing
system advance the goals of the organization? Another question that arises, which is more costeffective: implementing a new system or upgrading an existing system? The answers all depend
on the age of the system, infrastructure, and if the will new technology be able to interface
with the existing systems and more importantly the vision and goals of the organization.
Another important piece of the requirements is defining the scope of the project which means
defining what will be included and what will not be included in the project. This is important to
avoid what is called scope creep. That term is exactly what you may be thinking. With our vital
signs example, the requirements have all been set and as you move through the system
development life cycle, and someone says, oh by the way, can we modify the colors on the
medication administration screen. That would be considered scope creep. If every idea
identified from scope creep is incorporated into the project, it will have an impact on both the
budget and timeframe. Ideas will need to be put on a Parking Lot list for another project.
Moving to the Nursing diagnosis and this compares to the design phase. This is what you want
the system to look like. For example, what order do you want the vital signs to be presented on
the screen or with the example for the staffing schedule, for a particular shift, do you want to
see staff listed by alphabetical order or by work status or full-time, part-time, and PRN or be
able to sort?
Next is the Planning phase or development of the system. This is the actual coding of the
software and testing of the system. For example, with the design of the vital signs flowsheet we
want the data to flow over to the graphing sheet to be able to trend the vital signs. The system
is usually created and tested in what is called test environment or playground before being
loaded into the live environment. The testing process is completed again in the live
environment as not all workflows can be simulated in a test environment. There are key phases
for testing such as alpha testing, volume testing, integrated testing, beta testing and I will
encourage you to review these terms. Training of the users for the system usually occurs
during the planning phase and may continue on into the implementation phase.
The Implementation phase is time for go-live. The new elements are in the system and available
for the users. Critical issues are corrected during this phase as well.
Last is the evaluation or analysis phase. This is the process of monitoring the system for issues,
troubleshooting and correcting coding issues in the software. This is also the phase where we
look at the types of reports that can be generated or based on the available data what reports
can be created. That sums up the basic steps of the system development life cycle. I use these
steps in projects that are not related to informatics as this is a basis for project management.
Slide 4 – System Development Life Cycle Models
Based on the steps of the system development life cycle, McGonigle and Mastrian discuss 4
different methods for system design that incorporate variations of these steps.
The Waterfall Model which is one of the oldest methods and literally depicts a waterfall. There
are 6 phases. The output from each phase flows into or becomes the input for the next phase.
The steps are completed in sequential order. One of my past informatics roles, I was
responsible for the electronic health record for a small, local hospital. When I came onboard to
the role, before the hospital opened, the first step of determining feasibility and selection of
the system was already completed. We were joining another hospital system, so part of my role
was the analysis of the existing system, design and customize the system software with
specifics for our patient population. Next was to develop the testing process. All departments
assisted to see how information flowed from one department to another. After the hospital
opened and things settled down, then we were in the maintenance phase of monitoring the
system and worked on reporting. When requests were received to modify various parts of the
system then the waterfall model started all over again.
Next is the Rapid Prototyping or Rapid Application Development (RAD). This method provides a
fast way to add functionality through creating a prototype and testing. It is easier for users to
examine. Information is gathered through focus groups to build a prototype using real data.
When it is beta-tested meaning the end-users test the system and provide feedback. I used this
model at a local hospital when we needed to modify the patient assessment screens to better
fit the nursing workflow process.
Next is the Object-Oriented Systems Development (OOSD) which combines the logic of the
system development life cycle with a modeling and programming software. This takes real
objects and puts them into a computer simulation software program. Once the objects are
oriented within the software, all of the interaction or exchanges take place between objects.
For example, objects could be an emergency department, a patient, a nurse, and a front desk
clerk. They are added to the simulation software and you can see the patient flow process. This
is a really cool process. I have assisted with this model as well in a role where we were doing
time-studies for process improvement of patient flow.
Last is the Dynamic System Development Method (DSDM) which is highly iterative meaning
there is a repetitive process involved and requires a high level commitment of end-users for
involvement and providing input. I have not used this model as the places I have worked in the
past did not have staffing levels to be able to have end-users temporarily assigned to projects
rather than patient care.
This week’s topic for the discussion board is the system development life cycle. You will choose
one of the models presented and describe 2 advantages and 2 disadvantages of your chosen
approach. Be sure to review the guidelines for substantive posts and the grading rubric for
discussion boards.
Slide 5- Human-Technology
Next, I will discuss the human-technology interfaces. Anytime a human uses technology, there
is some type of hardware and/or software that enables and supports the interaction.
What are some examples of the human-technology interface? Examples would be driving a car,
using your cell phone, programing a PCA pump, and using the electronic health record.
This all seems straight forward, right? Well, what happens when you have a problem with the
technology? For example, the IV pump does not have the safety guardrails installed with the
newest upgrade. What do you do? Another example, the patient care tech doesn’t have the
ability to document the patient’s oxygen saturation rate in the electronic health record and you
as the RN need to know that information. These are real examples that I have witnessed.
The challenge with human-technology interfaces is that people try to circumvent the problem,
try to find a Band-Aid fix, and never address the real issue. The bottom-line, is that not
addressing these issues could put the patient at risk. It isn’t the technology causing the
problem, but it is an error in the design process. The goal is to design and test technology that
will enhance the user’s workflow and processes to provide safe patient care.
The assigned readings and videos will further expand on all of the topics that I have presented.
In addition, one last topic that I haven’t mentioned is terminology in nursing and that is covered
in the assigned readings.
Slide 6 – Module 2 Assignments
This week, there are 2 assignments.
The discussion board on the topic of the System Development Life Cycle and written paper
assignment on the human-technology interactions.
Be sure to review the instructions in the module and the rubrics prior to submitting your
assignments.
Slide 7 – Questions
If you have questions about this module, please post them on the Q&A board.
I hope you have a great week and don’t forget to smile!

Purchase answer to see full
attachment