Computerized Provider Order Entry (CPOE) Part 2
Continue CPOE study with advanced order sets, clinical decision support, and how CPOE integrates with EHR workflows.
By the end of this lesson you can
- Explain what clinical decision support does and where it fails
- Describe alert fatigue and why it is a safety problem
- Handle verbal and telephone orders correctly
- Track an order through to its result
Lesson Notes
Read through the key concepts before you try the challenge.
The alert that stopped working
You support a clinic using an EHR with extensive alerting.
The system fires an alert on almost every order — an interaction, a duplicate, a formulary note. Providers dismiss them in under a second, because dismissing is the only way to get through a clinic list. Then a genuinely dangerous interaction alert fires, and it is dismissed exactly like the other forty.
Your task: Understand why too much safety tooling produces less safety.
Clinical decision support is genuinely valuable: it catches allergy conflicts, drug interactions, duplicate orders, and dosing outside expected ranges. But every alert spends a small amount of the user's attention, and attention is finite. When the great majority of alerts are irrelevant, users learn — correctly, in a statistical sense — that dismissing is usually right.
| Requirement | Why |
|---|---|
| Read the order back to the provider | Confirms what you heard matches what they said, before anything is acted on |
| Record it immediately | Memory is not a record, and the order takes effect now |
| Note who gave it, and when | Attribution is what makes the order valid |
| Obtain the provider's countersignature within the required window | Organizational policy sets the window; the order is not complete without it |
An order placed is not a result received. Orders need tracking to completion, and the gap between the two is where results go missing — a specimen never collected, a study never scheduled, a referral never booked. Many EHRs have a pending-orders view for exactly this, and working it is often support staff's responsibility.
Order Sets & Clinical Decision Support
Most EHR systems include pre-built order sets — groups of orders commonly used together for specific diagnoses or procedures. Clinical Decision Support (CDS) alerts notify providers of potential drug interactions, allergies, or guideline deviations.
- Order sets speed up order entry and reduce omissions
- CDS alerts promote evidence-based prescribing
- Alert fatigue is a known challenge — too many alerts get ignored
CPOE Workflow Integration
When a provider enters an order through CPOE, it is immediately transmitted to the appropriate department — pharmacy, radiology, lab — without requiring paper transport. This reduces delays and transcription errors.
Challenge
Apply what you've learned in this lesson.
What is a known downside of Clinical Decision Support alerts?
Finished this lesson?
Progress is saved in this browser only. It is not a grade — official progress lives in Brightspace.