7.2 Workflows, Order Sets, and Pathways

7.2 Workflows, Order Sets, and Pathways

Quick Answer: Task A.4 also tests how care is packaged. Know order sets, care pathways, and protocols; who owns the content; and how specialty variation is controlled. A sepsis bundle that no one maintains is more dangerous than no bundle.

Section 7.1 was about functions—defaults, required fields, closed loops, time-to-task. This section is about the content containers those functions serve. CPHIMS will hand you a messy request (“build my sepsis set tonight,” “we need a pathway,” “nurses should just start lactate”) and expect you to pick the right artifact, the right owner, and the right amount of variation. Analytics and predictive models wait in chapter 8. CDS rule types wait in chapter 9. Here you are still in Domain 2 task A.4: system functionality that optimizes clinical effectiveness and efficiency.

CPHIMS practice questionsPractice questions with detailed explanations

Workflow is work-as-done

A workflow is the sequence of work as it actually happens—not only the swimlane drawn in a conference room. Informatics designs for work-as-done: who acts, in what order, with what exceptions, at 3 a.m. in the hallway. Work-as-imagined (“the physician always opens the enterprise set, then the nurse collects cultures, then pharmacy verifies within ten minutes”) is a hypothesis. If you do not watch the unit, you will automate the wrong sequence.

Before you add another set:

1. Observe the first hour of suspected sepsis where it really occurs.
2. Map who must act and what is currently waiting on whom.
3. Find the open loops—cultures sitting uncollected, antibiotics verified but not on the floor, lactate resulted to a pool nobody watches.
4. Decide which artifact (protocol, order set, pathway, or a later CDS advisory) removes the friction.
5. Only then build.

A best-practice advisory that nags “start the sepsis set” when the set takes 14 minutes and 22 required questions will be ignored. Functionality and workflow are one design.

Order sets

An order set is a grouped, typically condition- or procedure-specific collection of orders—laboratories, medications, imaging, nursing tasks, consults—that a clinician can accept, modify, or decline. It is a CPOE convenience and a standardization tool. It is not a personal preference list with the force of policy.

Good order sets:

• Are indication-named (“Adult suspected sepsis — ED”), not “Dr. Smith admission.”
• Pre-select the bundle elements; leave controversial or high-risk add-ons unchecked.
• Encode sequence where sequence is safety (draw blood cultures so they do not delay the first antimicrobial beyond the protocol window).
• Use coded catalog items, not free-text “give whatever antibiotic.”
• Show contraindications and weight or renal adjustments as visible defaults, not hidden assumptions.
• Carry a review date and a named owner.

Bad order sets:

• Personal sets that bypass pharmacy and therapeutics (P&T) and infection-prevention standards.
• “Everything for everybody” sets that explode pharmacy verification and bury the bundle.
• Sets that still contain retired drugs or stale timing language nobody updated after the last guideline change.
• Duplicate overlapping sets (ED sepsis, hospitalist sepsis, ICU sepsis) with conflicting first-line antibiotics and no shared core.

Bundles inside the set

A bundle is a small set of evidence-based actions that work better together than as optional à la carte items. The exam’s favorite example is a sepsis bundle order set: lactate, blood cultures, timely antimicrobials, and fluid resuscitation per the organization’s current protocol—not a 60-line ICU admission catalog. The point of a bundle is reliability of a few high-value steps, not completeness of every possible order.

If you dilute the bundle with optional vasopressors, a full respiratory panel, and a central-line kit, two things happen. Users either accept everything (automation bias from 7.1) or they abandon the set and free-text the antibiotic. Both destroy effectiveness.

Pathways and protocols

A care pathway (clinical pathway) is a multidisciplinary, time-oriented plan for a diagnosis or procedure—from first recognition through expected milestones and discharge. It includes orders, assessments, education, and handoffs. An order set is often one tool inside a pathway. Calling a single CPOE list a “pathway” is an exam trap.

A protocol or standing order is a pre-approved set of actions a nurse, pharmacist, or other designated clinician may start when criteria are met: hypoglycemia protocol, heparin nomogram, sepsis screening plus nurse-driven lactate and a first fluid bolus. Protocols need a named clinical owner, inclusion and exclusion criteria, and an audit trail. IT cannot “turn on a protocol” without that sponsorship.

A sepsis pathway might include triage screening, a nurse protocol for lactate, an ED order set, an ICU escalation path, and a quality abstract. The order set is necessary and not sufficient.

Specialty variation

One enterprise sepsis set for neonates, pregnant patients, immunocompromised oncology adults, and community-acquired ED adults will be ignored. Variation is legitimate when physiology, drug choice, or site of care differs. Variation is not legitimate when it is “how we have always done it on 4 West.”

The informatics pattern:

• A core bundle that is shared, locked, and evidence-owned.
• Specialty add-ons owned by that service (pediatric weight-based dosing, obstetric antibiotic choices, ED versus ward collection logistics).
• Shared naming and status so analytics can still see “sepsis bundle started.”
• No fork of 14 unmanaged copies that drift after the first month.

Font color preference is not a specialty. A personal laboratory panel that conflicts with the antibiogram is not a specialty. Those requests go through governance, not a same-night build.

Ownership of content

This is a high-yield CPHIMS item that looks like leadership but lives inside informatics. IT does not own clinical content. IT implements, versions, promotes across environments, and reports what is used.

A workable ownership model:

• Clinical owner (named person or role: ED medical director, CMIO designee, sepsis committee chair) approves indicated orders and clinical logic.
• Pharmacy / P&T owns medication products, concentrations, and restrictions.
• Nursing informatics owns nursing orders, BCMA exception paths, and protocol steps nurses execute.
• Quality / infection prevention owns bundle definitions and measure mapping—the CPHQ conversation inside the build.
• Health information / CDI owns documentation that must remain attributable and current—the RHIA conversation.
• Informatics / EHR analyst owns the build, version, how the set is found, and how status displays on the worklist.

Review cadence is part of ownership. High-risk sets—sepsis, anticoagulation, insulin, opioids—move on a short clock: after each relevant guideline or formulary change, and at least on a planned cycle. Retirement is a decision. An unowned set that still appears in search is an active safety defect.

When a physician asks for “my own sepsis set,” the exam answer is almost never “build it tonight.” Route the request through content governance, compare the extras to the enterprise bundle, and adopt the evidence—not the personality.

Scenarios and exam traps

Scenario — 60-line sepsis set. The enterprise “sepsis” set includes the bundle plus optional vasopressors, a full respiratory viral panel, and central-line orders, all pre-checked. ED physicians stop using it and free-text cefepime. Effectiveness falls. Split a short, indication-named ED set with the core bundle pre-selected; park extras as unchecked add-ons or a separate ICU set with its own owner.

Scenario — personal sets versus the antibiogram. A hospitalist emails the analyst at 16:00: build my personal sepsis set tonight; the enterprise set is missing my favorite extra labs and my preferred fluoroquinolone. The CPHIMS response is governance, not heroics. Compare the labs to the bundle. Send the fluoroquinolone through P&T and infection prevention. Do not fork an unmanaged copy that will never be reviewed.

Scenario — pathway with no protocol. Leadership announces a “sepsis pathway,” but lactate still waits for a new physician order and nurses have no standing criteria. You built an order set and called it a pathway. Add a nurse protocol with a clinical owner if the evidence and medical staff support it; then connect the set and the later milestones.

Watch these traps:

1. Equating an order set with a pathway.
2. Letting IT own clinical logic because analysts can click the build tools.
3. Treating more pre-checked orders as more complete care.
4. Unmanaged specialty or personal copies that drift.
5. No review date, no retirement path.
6. A BPA that nags people into a set that is too slow to use.

Get the package and the owner right, and chapter 7.3’s safety design has something trustworthy to protect.