You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,8 +15,8 @@ decision support from within a clinician's workflow. The API supports:
15
15
User activity inside the clinician's workflow triggers **CDS hooks** in real-time. For example:
16
16
17
17
*`patient-view` when opening a new patient record
18
-
*`medication-prescribe` on authoring a new prescription
19
-
*`order-review` on viewing pending orders for approval
18
+
*`order-select` when selecting one or more orders to place for a patient
19
+
*`order-sign` immediately before an order is signed
20
20
21
21
When a triggering activity occurs, the CDS Client notifies each CDS service registered for the activity. These services must then provide near-real-time feedback about the triggering event. Each service gets basic details about the clinical workflow
22
22
context (via the `context` parameter of the hook) plus whatever
0 commit comments