INP402 EpicCare Inpatient Clinical — Enhanced Study
Guide
Original exam-focused companion for Epic inpatient clinical workflows, documentation, navigation, and patient-care coordination
Source orientation: The supplied Stuvia listing is a 75-page, 2025/2026 Q&A;/exam-elaboration document titled “INP402
EPICCARE INPATIENT CLINICAL EXAM Actual Exam 2026/2027 176 Questions Complete and Verified Answers Pass
Guaranteed - A+ Graded.” Its public preview covers inpatient workflow and navigators, flowsheets, orders, SmartForms, Patient
Lists, SmartLinks, and order management. ■cite■turn0view0■
Expanded scope: Related public INP402 materials identify additional areas such as flowsheet fundamentals, charges/custom
formulas, required documentation, preference lists/profiles, I&O;, LDA build, navigation, rule editor/record fields, release/build
settings, calculated assessments, task templates/worklists, care plans, and education. ■cite■turn0search2■turn0search6■
Important: Epic configurations vary by organization, role, version, security, and local build. This guide teaches transferable
concepts rather than asserting that every institution uses identical buttons, names, or workflows.
Copyright note: This is original educational material. It does not reproduce the paid Stuvia document or inaccessible exam
questions.
1. Inpatient Workflow & Navigators
Inpatient workflows are organized around efficient access to patient context, documentation, orders, results, communication, and
care coordination. A Navigator can bring related activities together while role-based configuration determines what users see.
The best workflow minimizes duplicate entry and unnecessary chart navigation.
Q: A clinician needs a rapid overview of active orders, recent vitals, I&O;, medications, allergies, and problems. What is the
general design principle?
Answer: Use an appropriately configured inpatient summary/dashboard that consolidates high-value information for the user's
role.
Exam trap: Do not assume that a similarly named ambulatory and inpatient activity behaves identically.
2. Flowsheet Fundamentals
Flowsheets provide structured documentation of discrete clinical observations such as vital signs, assessments, I&O;, devices,
and other patient-care data. Templates organize groups, and groups organize related rows. Structured data supports trending,
reporting, and downstream decision support.
Q: Why is structured flowsheet documentation preferable to typing a measurement into free text?
Answer: Discrete data can be trended, queried, validated, reused, and made available to downstream clinical workflows.
Exam trap: A free-text note may communicate context but is usually not a substitute for required discrete documentation.
3. Flowsheet Rows, Groups & Templates
A useful mental model is Template → Group → Row. Templates organize documentation domains, groups cluster related items,
and rows represent specific documentation elements. Build/configuration terminology can differ by Epic implementation.
Q: What does the Template → Group → Row hierarchy help an analyst understand?
Answer: It explains how clinical documentation is organized from a high-level activity down to specific discrete data elements.
Exam trap: Do not confuse a display container with the underlying clinical data element.
4. Intake & Output Documentation
I&O; documentation should capture relevant intake sources and output sources consistently. Accurate timestamps, units,
route/source, and device context matter because I&O; can influence fluid-balance assessment and clinical decisions.
Q: A patient has a new NG tube. What is the preferred documentation concept for its output?
Answer: Capture it in a structured, appropriate I&O;/flowsheet row rather than burying the value in a free-text comment.
INP402 EpicCare Inpatient Clinical — Enhanced Study Guide Page 1
, Exam trap: A one-time workflow need does not necessarily justify permanent build changes.
5. Lines, Drains & Airways (LDA)
LDA documentation links devices to patient safety and clinical context. Important concepts include device type, location/site,
insertion or assessment details, status, output when applicable, and removal. Local build determines exact fields.
Q: Why is structured LDA documentation clinically useful?
Answer: It makes device presence and related assessments visible, consistent, and reportable across the care team.
Exam trap: Do not assume every device uses identical documentation fields.
6. Orders & CPOE
Computerized provider order entry supports standardized ordering, decision support, status tracking, modifications,
discontinuation, and signature workflows. Order integrity requires an audit trail; clinical systems generally preserve the history
rather than permitting arbitrary deletion.
Q: What is the key difference between discontinuing an order and deleting its history?
Answer: Discontinuation changes the order's active status while preserving an auditable record.
Exam trap: Never treat the electronic record like a word-processing document where historical actions can simply be erased.
7. Medication Administration & eMAR
Medication workflows connect orders, verification, administration, documentation, scheduling, and clinical monitoring. Safe use
requires checking the active order, patient, medication, dose, route, timing, relevant parameters, allergies, and local policy.
Q: Why should a nurse avoid relying only on a copied medication list?
Answer: Medication status can change; the current active order and administration record provide the relevant operational
context.
Exam trap: Medication reconciliation and medication administration are related but distinct workflows.
8. Clinical Documentation & Notes
Good clinical documentation is accurate, timely, relevant, internally consistent, and attributable. Structured data and narrative can
complement one another. Templates and SmartTools should support—not replace—clinical judgment and individualized
documentation.
Q: What is the safest principle when using a documentation template?
Answer: Verify every populated element and edit it so the final record accurately reflects the current patient.
Exam trap: Auto-populated text can become inaccurate if copied forward without verification.
9. SmartTools: SmartLinks, SmartTexts & SmartPhrases
SmartTools can reduce repetitive typing and connect reusable content or discrete patient data to documentation. SmartLinks
generally retrieve dynamic patient-specific information; SmartPhrases provide reusable text; SmartTexts/templates provide
structured reusable documentation content.
Q: What is the major safety risk of a dynamic documentation tool?
Answer: Assuming that automatically inserted information is current or appropriate without verifying it.
Exam trap: Automation reduces typing; it does not remove the clinician's responsibility for accuracy.
10. SmartForms & Structured Documentation
SmartForms can present structured fields such as checkboxes, lists, and other discrete inputs. When appropriately mapped,
structured documentation can support reuse in notes and other workflows.
Q: Why are SmartForms valuable for structured clinical workflows?
INP402 EpicCare Inpatient Clinical — Enhanced Study Guide Page 2
Guide
Original exam-focused companion for Epic inpatient clinical workflows, documentation, navigation, and patient-care coordination
Source orientation: The supplied Stuvia listing is a 75-page, 2025/2026 Q&A;/exam-elaboration document titled “INP402
EPICCARE INPATIENT CLINICAL EXAM Actual Exam 2026/2027 176 Questions Complete and Verified Answers Pass
Guaranteed - A+ Graded.” Its public preview covers inpatient workflow and navigators, flowsheets, orders, SmartForms, Patient
Lists, SmartLinks, and order management. ■cite■turn0view0■
Expanded scope: Related public INP402 materials identify additional areas such as flowsheet fundamentals, charges/custom
formulas, required documentation, preference lists/profiles, I&O;, LDA build, navigation, rule editor/record fields, release/build
settings, calculated assessments, task templates/worklists, care plans, and education. ■cite■turn0search2■turn0search6■
Important: Epic configurations vary by organization, role, version, security, and local build. This guide teaches transferable
concepts rather than asserting that every institution uses identical buttons, names, or workflows.
Copyright note: This is original educational material. It does not reproduce the paid Stuvia document or inaccessible exam
questions.
1. Inpatient Workflow & Navigators
Inpatient workflows are organized around efficient access to patient context, documentation, orders, results, communication, and
care coordination. A Navigator can bring related activities together while role-based configuration determines what users see.
The best workflow minimizes duplicate entry and unnecessary chart navigation.
Q: A clinician needs a rapid overview of active orders, recent vitals, I&O;, medications, allergies, and problems. What is the
general design principle?
Answer: Use an appropriately configured inpatient summary/dashboard that consolidates high-value information for the user's
role.
Exam trap: Do not assume that a similarly named ambulatory and inpatient activity behaves identically.
2. Flowsheet Fundamentals
Flowsheets provide structured documentation of discrete clinical observations such as vital signs, assessments, I&O;, devices,
and other patient-care data. Templates organize groups, and groups organize related rows. Structured data supports trending,
reporting, and downstream decision support.
Q: Why is structured flowsheet documentation preferable to typing a measurement into free text?
Answer: Discrete data can be trended, queried, validated, reused, and made available to downstream clinical workflows.
Exam trap: A free-text note may communicate context but is usually not a substitute for required discrete documentation.
3. Flowsheet Rows, Groups & Templates
A useful mental model is Template → Group → Row. Templates organize documentation domains, groups cluster related items,
and rows represent specific documentation elements. Build/configuration terminology can differ by Epic implementation.
Q: What does the Template → Group → Row hierarchy help an analyst understand?
Answer: It explains how clinical documentation is organized from a high-level activity down to specific discrete data elements.
Exam trap: Do not confuse a display container with the underlying clinical data element.
4. Intake & Output Documentation
I&O; documentation should capture relevant intake sources and output sources consistently. Accurate timestamps, units,
route/source, and device context matter because I&O; can influence fluid-balance assessment and clinical decisions.
Q: A patient has a new NG tube. What is the preferred documentation concept for its output?
Answer: Capture it in a structured, appropriate I&O;/flowsheet row rather than burying the value in a free-text comment.
INP402 EpicCare Inpatient Clinical — Enhanced Study Guide Page 1
, Exam trap: A one-time workflow need does not necessarily justify permanent build changes.
5. Lines, Drains & Airways (LDA)
LDA documentation links devices to patient safety and clinical context. Important concepts include device type, location/site,
insertion or assessment details, status, output when applicable, and removal. Local build determines exact fields.
Q: Why is structured LDA documentation clinically useful?
Answer: It makes device presence and related assessments visible, consistent, and reportable across the care team.
Exam trap: Do not assume every device uses identical documentation fields.
6. Orders & CPOE
Computerized provider order entry supports standardized ordering, decision support, status tracking, modifications,
discontinuation, and signature workflows. Order integrity requires an audit trail; clinical systems generally preserve the history
rather than permitting arbitrary deletion.
Q: What is the key difference between discontinuing an order and deleting its history?
Answer: Discontinuation changes the order's active status while preserving an auditable record.
Exam trap: Never treat the electronic record like a word-processing document where historical actions can simply be erased.
7. Medication Administration & eMAR
Medication workflows connect orders, verification, administration, documentation, scheduling, and clinical monitoring. Safe use
requires checking the active order, patient, medication, dose, route, timing, relevant parameters, allergies, and local policy.
Q: Why should a nurse avoid relying only on a copied medication list?
Answer: Medication status can change; the current active order and administration record provide the relevant operational
context.
Exam trap: Medication reconciliation and medication administration are related but distinct workflows.
8. Clinical Documentation & Notes
Good clinical documentation is accurate, timely, relevant, internally consistent, and attributable. Structured data and narrative can
complement one another. Templates and SmartTools should support—not replace—clinical judgment and individualized
documentation.
Q: What is the safest principle when using a documentation template?
Answer: Verify every populated element and edit it so the final record accurately reflects the current patient.
Exam trap: Auto-populated text can become inaccurate if copied forward without verification.
9. SmartTools: SmartLinks, SmartTexts & SmartPhrases
SmartTools can reduce repetitive typing and connect reusable content or discrete patient data to documentation. SmartLinks
generally retrieve dynamic patient-specific information; SmartPhrases provide reusable text; SmartTexts/templates provide
structured reusable documentation content.
Q: What is the major safety risk of a dynamic documentation tool?
Answer: Assuming that automatically inserted information is current or appropriate without verifying it.
Exam trap: Automation reduces typing; it does not remove the clinician's responsibility for accuracy.
10. SmartForms & Structured Documentation
SmartForms can present structured fields such as checkboxes, lists, and other discrete inputs. When appropriately mapped,
structured documentation can support reuse in notes and other workflows.
Q: Why are SmartForms valuable for structured clinical workflows?
INP402 EpicCare Inpatient Clinical — Enhanced Study Guide Page 2
