|
Type
|
Reference
|
Content
|
|
web
|
github.com
|
CDS Hooks Library, published by Clinical Decision Support WG. This guide is not an authorized publication; it is the continuous build for version 2.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/cds-hooks-library/
and changes regularly. See the Directory of published versions
|
|
web
|
github.com
|
PR #31
: Added logical models defining the hook-specific context for appointment-book
, encounter-discharge
, encounter-start
, order-dispatch
, order-select
, order-sign
and patient-view
, so hook contexts can be validated with the FHIR Validator, including the ord-1
invariant requiring user, performer and selection references to be in the form [ResourceType]/[id]
, and added a Schemas menu entry (applied here
, here
, here
, here
, here
, here
, here
and here
)
|
|
web
|
github.com
|
PR #23
: Corrected the order-dispatch
example and the fulfillmentTasks
description to use the context field name dispatchedOrders
rather than dispatched-orders
(applied here
and here
)
|
|
web
|
github.com
|
PR #26
: Declared the standards status of each page in the Implementation Guide ( draft
for medication-refill
and problem-list-item-create
, trial-use
otherwise) and removed the hard-coded status statements from the appointment-book
, encounter-discharge
, encounter-start
, medication-refill
, medication-verify
, order-select
, order-sign
, patient-view
and template pages
|
|
web
|
github.com
|
PR #29
: Added guidance to the hook documentation template recommending a workflow diagram for new hooks (applied here
)
|
|
web
|
github.com
|
Technical correction ( PR #33
, PR #34
): Corrected typographical errors and formatting, including in the template page markup (applied here
, here
, here
, here
, here
, here
, here
, here
and here
)
|
|
web
|
github.com
|
Technical correction ( PR #33
, PR #34
): Corrected typographical errors and formatting, including in the template page markup (applied here
, here
, here
, here
, here
, here
, here
, here
and here
)
|
|
web
|
github.com
|
Hook maturity:
Is the maturity level assigned to each hook (shown in the Hooks
list and on each hook page) accurate, based on known implementations? Please also record implementations on the CDS Hooks Availability
page.
|
|
web
|
github.com
|
The CDS Hooks Library contains specifications of industry standardized clinical workflow steps upon which remote clinical decision support can be requested. The Library is an HL7 publication with mixed standards status
: the patient-view
and order-sign
hooks are Normative, and the remaining hooks are each published at the status shown on their page (Standard for Trial Use, Draft, or Deprecated). The names of the below hooks hyperlink to their individual specification and the number following their name indicates their specific maturity, according to the CDS Hooks Maturity Model
. Because hook maturity is based on the extent of implementation, client and CDS Service implementations of each hook are tracked on the CDS Hooks Availability
page, and implementers are encouraged to add their own implementations there. All hooks are intended to be used by systems conforming to the HL7 CDS Hooks Implementation Guide
.
|
|
web
|
cds-hooks.org
|
See https://cds-hooks.org/
for additional information, resources and ways to get involved.
|
|
web
|
github.com
|
CDS Hooks is the copyright of HL7 International and Boston Children's Hospital. The CDS Hooks specification is licensed under a Creative Commons Attribution 4.0 International License. All source code for CDS Hooks is available at https://github.com/cds-hooks
.
|
|
web
|
github.com
|
This hook is deprecated in favor of the order-select
and order-sign
hooks, with the goal of clarifying workflow trigger points and supporting orders beyond medications. In this refactoring, medication-prescribe
and order-review
hooks are being deprecated in favor of newly created
order-select
and
order-sign
hooks. This notice is a placeholder to this effect while CDS Hooks determines the appropriate process for deprecating hooks
.
|
|
web
|
www.bottlecaps.de
|
Consider creating a diagram to illustrate the workflow in which this hook is called. The order-sign workflow diagram
was created with a tool like: Railroad Diagram Generator
.
|