Skip to content
← back
§ SELECTED / STANDARDS + IA

CDS Hooks Configuration

Clinical decision support — the alerts and guidance an EHR surfaces mid-workflow — configured through one system I designed to work across three different EHRs.

PROVES
Cross-EHR information architecture + the judgment to push back.
STATUS
Case study
§ 01

Overview

The PM's spec organized configuration around CDS hooks — the technical trigger points. I argued the admin audience thinks in clinical roles, not hooks, and proposed a role-based model instead. It was adopted.

Shipped with a two-state conditional form, a banner-plus-inline error pattern backed by a full error inventory, and a clinician-facing guidance panel.

§ 02

Selected frames

The guidance panel living inside the EHR workflow
Clinical decision support panel shown in context inside the EHR interface
Clinical Guidance panel — severity-ranked cards, urgent-first
Clinical Guidance sidebar showing critical guidance cards sorted by urgency, with sort and severity filters
Admin configuration — the role-based model that replaced hook-first
CDS Hooks admin configuration screen organized by clinical roles
Admin configuration — service and error states
CDS Hooks admin configuration screen showing service configuration and error states