Written and maintained by CASRAI Editorial Board
Last updated
The 5 Rights of CDS (Five Rights of Clinical Decision Support) is the foundational health informatics design and governance framework—formulated by Jerome A. Osheroff and colleagues (2007/2012) and adopted by the Agency for Healthcare Research and Quality (AHRQ), HIMSS, and the ONC—stating that effective clinical decision support must deliver the right information, to the right person, in the right intervention format, through the right channel, at the right point in the workflow.
What Are the Five Rights of Clinical Decision Support?
Adapted conceptually from the classic “Five Rights of Medication Administration” in nursing safety, the Five Rights of Clinical Decision Support explains why many well-intentioned electronic health record (EHR) pop-up alerts fail to improve patient outcomes and instead generate severe clinician alert fatigue (with published override rates of 49% to 96% for poorly targeted interruptive medication and Best Practice Advisory alerts). An alert that contains accurate medical guideline text (right information) will still fail if it interrupts the wrong clinician (wrong person), uses a disruptive modal pop-up when a default order set was needed (wrong format), or fires at chart closure after the patient has already left the room (wrong point in workflow).
| The 5 Rights Dimension | Core Design Question | Compliant EHR Implementation Example | Common Failure Mode (Alert Fatigue Trigger) |
|---|---|---|---|
| 1. The Right Information | Is the clinical knowledge evidence-based, patient-specific, contextualized to current labs/meds, and immediately actionable? | Calculating patient-specific creatinine clearance (CrCl) and displaying the exact renal-adjusted vancomycin or DOAC dose. | Firing a generic “Renal dosing caution” banner even when the patient’s eGFR is >90 mL/min/1.73m². |
| 2. The Right Person | Who on the care team (physician, pharmacist, RN, MA, or patient) has the scope of practice and workflow role to act on this guidance? | Routing routine influenza/pneumococcal immunization care gaps to the rooming medical assistant under standing orders. | Firing preventive screening and social-history reminders as interruptive pop-ups to an attending surgeon during post-op sign-off. |
| 3. The Right Intervention Format | Should the CDS be an order set, pre-checked default, documentation template, info-button, non-interruptive nudge, or hard-stop alert? | Pre-selecting weight-based VTE prophylaxis inside the inpatient admission order set (passive choice architecture). | Using a modal interruptive pop-up alert (Epic BPA) for every low-severity clinical reminder. |
| 4. The Right Channel | Which technical interface (EHR desktop CPOE, mobile Haiku/rover, smart IV pump, patient portal, or SMS) reaches the decision-maker? | Delivering pre-visit bowel prep instructions and medication hold reminders directly to the patient’s mobile phone via SMS/portal. | Displaying an urgent critical lab deterioration alert only inside an unmonitored desktop EHR inbox folder. |
| 5. The Right Point in the Workflow | At what exact cognitive and operational moment is the clinical decision being made? | Displaying guideline-concordant antibiotic choices during order-select before the clinician chooses a broad-spectrum agent. |
Firing an alert at order-sign or chart closure after the clinician has already discussed a different plan with the patient. |
Technical Mapping: How the 5 Rights Align with HL7 FHIR and CDS Hooks
In modern interoperable clinical decision support systems (CDSS), the Five Rights are operationalized programmatically using HL7 FHIR R4, Clinical Quality Language (CQL), and the HL7 CDS Hooks specification:
- Right Information (`CQL` + `Prefetch` Context): Rather than evaluating static ICD-10 diagnosis codes alone, the CDS service uses FHIR `prefetch` templates to pull real-time `Patient`, `Observation` (labs/vitals), `MedicationRequest`, and `AllergyIntolerance` resources, executing deterministic CQL logic or validated Software as a Medical Device (SaMD) / non-device CDS risk models.
- Right Person (`context.userId` Practitioner Role Filtering): The CDS service inspects the FHIR `PractitionerRole` of the active user (`context.userId`) so nursing assessments route to `RN` roles, pharmacy verification alerts route to `Pharmacist` roles, and diagnostic ordering guidance routes to `Physician`/`NP`/`PA` roles.
- Right Intervention Format (CDS Hooks `cards`, `suggestions`, and `systemActions`): CDS Hooks responses support graduated intervention formats—from informational links (`indicator: “info”`), warning cards with one-click order replacement `suggestions` (`indicator: “warning”`), to critical hard-stops (`indicator: “critical”`) or silent form pre-population (`systemActions`).
- Right Point in the Workflow (Standardized Hook Triggers): HL7 CDS Hooks defines explicit workflow trigger points—including `patient-view` (chart open), `Appointment-book` (scheduling), `order-select` (initial item selection in CPOE), `order-sign` (final signature), and `encounter-discharge`—allowing health IT architects to shift clinical decision support tools upstream to the moment of choice.
EHR Governance & Implementation Checklist: Auditing Alerts Against the 5 Rights
Hospital CDS governance committees and Chief Medical Information Officers (CMIOs) use the following operational checklist before approving any new EHR alert or during quarterly alert-fatigue rationalization audits:
5 RIGHTS OF CDS — EHR INTERVENTION DESIGN & AUDIT CHECKLIST
1. RIGHT INFORMATION AUDIT
[ ] Is the clinical logic backed by a named, current CPG (e.g., ACC/AHA, IDSA, USPSTF) or
locally validated predictive model with documented ONC HTI-1 source attributes?
[ ] Does the suppression logic exclude patients for whom the action is already completed,
contraindicated, or clinically irrelevant (e.g., comfort care / hospice)?
[ ] Does the alert display the specific patient data points (e.g., last K+ value and timestamp)
that triggered the recommendation so the clinician does not have to leave the screen?
2. RIGHT PERSON AUDIT
[ ] Is the alert restricted by role/security class and clinical department/specialty to the
exact team member empowered to execute the action?
[ ] Can this task be delegated upstream to a medical assistant, nurse, or pharmacist via a
standing order protocol or workqueue instead of interrupting the physician?
3. RIGHT INTERVENTION FORMAT AUDIT
[ ] Have non-interruptive formats (order set defaults, documentation smart-lists, flowsheet
highlighting, passive banner nudges) been evaluated before choosing a pop-up alert?
[ ] Does the intervention provide a 1-click actionable button (e.g., "Order Stat ECG now" or
"Discontinue duplicate order") inside the card rather than text-only advice?
4. RIGHT CHANNEL AUDIT
[ ] Is the delivery channel matched to urgency and care setting (e.g., inpatient CPOE vs.
secure mobile push vs. patient portal pre-visit message)?
5. RIGHT POINT IN WORKFLOW AUDIT
[ ] Does the intervention fire BEFORE the clinician invests cognitive effort in an alternative
plan (e.g., at order selection or pre-visit planning rather than chart sign-off)?
[ ] Is there a 30-day and 90-day post-go-live monitoring plan tracking firing volume,
acceptance rate, override reasons, and unintended workflow workarounds?Frequently Asked Questions
What are the five rights of clinical decision support?
The Five Rights of Clinical Decision Support (5 Rights of CDS) state that to measurably improve clinical care and patient safety, a CDS system must communicate: (1) the right information (evidence-based, patient-specific, actionable knowledge), (2) to the right person (the care team member or patient responsible for the action), (3) in the right intervention format (order set, template, passive nudge, or alert), (4) through the right channel (EHR, mobile device, smart pump, or portal), and (5) at the right point in the workflow (at the exact moment the clinical decision is made).
How do the 5 Rights of CDS reduce EHR alert fatigue?
Applying the 5 Rights of CDS reduces alert fatigue by replacing high-volume, low-specificity interruptive pop-up alerts with upstream workflow design: filtering out clinically irrelevant firings (Right Information), routing routine preventive tasks to medical assistants or pharmacists rather than physicians (Right Person), converting pop-ups into pre-checked order set defaults or passive inline guidance (Right Format), and presenting guidance during order selection rather than after order entry (Right Point in Workflow).
