For hospital-based clinical tool usage, which security class is recommended?

For hospital-based clinical tool usage, which security class is recommended?

• A. Epiccare
• B. Inpatient
• C. Role
• D. Navigators

Answer: (B)

Security classes in Epic map users to the care setting they work in, guiding what clinical tools and patient data they can access. For hospital-based clinical tool usage, the Inpatient class lines up with the hospital inpatient workflow, enabling access to inpatient encounters, bed assignments, admission/discharge processes, inpatient medication administration, and inpatient-specific charts and flowsheets. This alignment helps clinicians work in the correct patient context and use tools that are relevant to inpatient care, while keeping data boundaries appropriate between inpatient and outpatient care. Other options aren’t security classes designed for this environment: Epiccare is a product/interface name, not a security class; Role is a broader access construct rather than a setting-specific scope; Navigators do not represent a standard inpatient security classification.

Security classes in Epic map users to the care setting they work in, guiding what clinical tools and patient data they can access. For hospital-based clinical tool usage, the Inpatient class lines up with the hospital inpatient workflow, enabling access to inpatient encounters, bed assignments, admission/discharge processes, inpatient medication administration, and inpatient-specific charts and flowsheets. This alignment helps clinicians work in the correct patient context and use tools that are relevant to inpatient care, while keeping data boundaries appropriate between inpatient and outpatient care. Other options aren’t security classes designed for this environment: Epiccare is a product/interface name, not a security class; Role is a broader access construct rather than a setting-specific scope; Navigators do not represent a standard inpatient security classification.