INP 402 ACTUAL QUESTIONS AND
CORRECT ANSWERS COMPLETE STUDY
GUIDE PACK
●● false
Answer: true or false: flowsheet rows, groups, and templates are stored
in the same master file
●● FLT
Answer: each flowsheet template is a record in what master file?
●● FLO
Answer: Groups and rows are records in what master file?
●● user experience
Answer: aims to create meaning behind tasks in the system by focusing
on the capabilities of users, how those users feel, and the emotional
connection users have with the system.
●● usability
Answer: is a part of the overall user experience and focuses on
understanding what users do, making those tasks easy to accomplish,
and removing roadblocks to task completion.
,●● heuristics
Answer: simple rules that you can use to approximate a larger probable
truth from smaller truths that are easier to observe. general rules of
thumb that can be used to help make decisions
●● system matches real world
Answer: heuristic where system should speak the users' language with
words, phrases, and concepts familiar to the user. follow real-world
conventions, making information appear in a natural and logical order.
examples are: print groups and reports with intuitive names; navigators,
activities, and toolbars in right order
●● Consistency and Standards
Answer: heuristic where users should not have to wonder whether
different words, situations, or actions mean the same thing. Follow
platform conventions. examples are: words like similar tools and uses
org's terminology and naming conventions
●● recognition, not recall
Answer: heuristic where minimize user's memory load by making
objects, actions, and options visible. the user should not have to
remember information from one part of the dialogue to another.
instructions for use of the build should be visible or easily retrievable.
examples are: toolbars and startup activities provide shortcuts
,●● Flexibility and Efficiency
Answer: heuristic where accelerators - unseen by the novice user - may
often speed up the interaction for the expert user such that the system
can cater to both inexperienced and experienced users. Allow users to
tailor frequent actions. examples are: providing tools for workflows, but
not creating clutter and users ability to re-arrange screen elements
(menus) to suit their needs.
●● simplicity and minimalist design
Answer: dialogues should not contain information that is irrelevant or
rarely needed. every extra unit of information in a dialogue competes
with the relevant units of information and diminishes their relative
visibility. examples are: category lists avoid too much irrelevant
information
●● help and documentation
Answer: heuristic where even though it is better if the build can be used
without documentation, it may be necessary to provide some. Any such
information should be easy to search, focused on the user's task, list
concrete steps to be carried out, and not too large. examples are: provide
quick reference materials
●● row
Answer: where data is documented, row with normal sized, black font in
flowsheet activity
, ●● template
Answer: seen as a "tab" in flowsheet activity. used to organize different
categories of documentation
●● group
Answer: used to organize individual documentation rows; row with
bigger, colorful font in the flowsheet activity
●● details report
Answer: what is C, provides clinicians extra details about the row they
are documenting in, like minimum and maximum values, and who
documented on the row last.
●● flowsheet group
Answer: what is E
●● flowsheet row
Answer: what is B
●● flowsheet template
Answer: what is A
CORRECT ANSWERS COMPLETE STUDY
GUIDE PACK
●● false
Answer: true or false: flowsheet rows, groups, and templates are stored
in the same master file
●● FLT
Answer: each flowsheet template is a record in what master file?
●● FLO
Answer: Groups and rows are records in what master file?
●● user experience
Answer: aims to create meaning behind tasks in the system by focusing
on the capabilities of users, how those users feel, and the emotional
connection users have with the system.
●● usability
Answer: is a part of the overall user experience and focuses on
understanding what users do, making those tasks easy to accomplish,
and removing roadblocks to task completion.
,●● heuristics
Answer: simple rules that you can use to approximate a larger probable
truth from smaller truths that are easier to observe. general rules of
thumb that can be used to help make decisions
●● system matches real world
Answer: heuristic where system should speak the users' language with
words, phrases, and concepts familiar to the user. follow real-world
conventions, making information appear in a natural and logical order.
examples are: print groups and reports with intuitive names; navigators,
activities, and toolbars in right order
●● Consistency and Standards
Answer: heuristic where users should not have to wonder whether
different words, situations, or actions mean the same thing. Follow
platform conventions. examples are: words like similar tools and uses
org's terminology and naming conventions
●● recognition, not recall
Answer: heuristic where minimize user's memory load by making
objects, actions, and options visible. the user should not have to
remember information from one part of the dialogue to another.
instructions for use of the build should be visible or easily retrievable.
examples are: toolbars and startup activities provide shortcuts
,●● Flexibility and Efficiency
Answer: heuristic where accelerators - unseen by the novice user - may
often speed up the interaction for the expert user such that the system
can cater to both inexperienced and experienced users. Allow users to
tailor frequent actions. examples are: providing tools for workflows, but
not creating clutter and users ability to re-arrange screen elements
(menus) to suit their needs.
●● simplicity and minimalist design
Answer: dialogues should not contain information that is irrelevant or
rarely needed. every extra unit of information in a dialogue competes
with the relevant units of information and diminishes their relative
visibility. examples are: category lists avoid too much irrelevant
information
●● help and documentation
Answer: heuristic where even though it is better if the build can be used
without documentation, it may be necessary to provide some. Any such
information should be easy to search, focused on the user's task, list
concrete steps to be carried out, and not too large. examples are: provide
quick reference materials
●● row
Answer: where data is documented, row with normal sized, black font in
flowsheet activity
, ●● template
Answer: seen as a "tab" in flowsheet activity. used to organize different
categories of documentation
●● group
Answer: used to organize individual documentation rows; row with
bigger, colorful font in the flowsheet activity
●● details report
Answer: what is C, provides clinicians extra details about the row they
are documenting in, like minimum and maximum values, and who
documented on the row last.
●● flowsheet group
Answer: what is E
●● flowsheet row
Answer: what is B
●● flowsheet template
Answer: what is A
