IP Review

Unattributed Code Systems

http://unstats.un.org/unsd/methods/m49/m49.htm

Copyright Fragment

This fragment is available on en/index.html

No use of external IP

Copyright and Registered Trademark Uses

IG © 2019+ HL7 International / Clinical Decision Support. Package hl7.fhir.uv.cds-hooks-clinical-reasoning#1.0.0-draft based on FHIR 4.0.1. Generated 2025-11-04 Links: Table of Contents | QA Report | Version History | CC0 | Propose a change ( src )
hl7.fhir.us.hai: Healthcare Associated Infection Implementation Guide ®© HL7 | CC0 ( src )
Using FHIR Clinical Reasoning with CDS Hooks, published by HL7 International / Clinical Decision Support. This guide is not an authorized publication; it is the continuous build for version 1.0.0-draft built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/cds-hooks-clinical-reasoning/ and changes regularly. See the Directory of published versions ( src )

External References

Type Reference Content

web github.com Using FHIR Clinical Reasoning with CDS Hooks, published by HL7 International / Clinical Decision Support. This guide is not an authorized publication; it is the continuous build for version 1.0.0-draft built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/cds-hooks-clinical-reasoning/ and changes regularly. See the Directory of published versions

Type	Reference	Content
web	github.com	Using FHIR Clinical Reasoning with CDS Hooks, published by HL7 International / Clinical Decision Support. This guide is not an authorized publication; it is the continuous build for version 1.0.0-draft built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/cds-hooks-clinical-reasoning/ and changes regularly. See the Directory of published versions
web	github.com
web	cds-hooks.org	Note that this topic is a very high-level approach to using CDS Hooks to support these two use cases. It is not a normative description of any of the CDS Hooks content. Please refer to the CDS Hooks specification itself for more details. At the time of this publication, the CDS Hooks specification has been balloted but is still in the process of being published. Because the links on this page deep-link the CDS Hooks specification, they are still referencing the original CDS Hooks specification. When it is published, the CDS Hooks specification will be located at http://cds-hooks.hl7.org .
web	cds-hooks.org	The first phase in consuming a CDS Service using CDS Hooks is to configure the integration from the EHR. The CDS Service publishes a set of endpoints to advertise available functionality using the discovery endpoint. For each endpoint, the service declares the hook during which it expects to be invoked, and optionally, any prefetch information that could be provided to the service.
web	cds-hooks.org	Each hook identifies contextual information that is available within the EHR. For example, the `order-sign` hook specifies the patient in context, as well as the orders being signed. When invoking the service from this hook, the EHR is expected to provide this contextual information as part of the request.
web	cds-hooks.org	In addition, the CDS Service may specify additional information using prefetch templates. Each prefetch template is a FHIR query URL, parameterized by the data available in context, and describing information needed by the CDS Service to perform its processing. By providing this information as part of the request, the EHR alleviates the need for the CDS Service to request the additional information.
web	cds-hooks.org	The second phase is the actual request/response call to the CDS Service. Once the integration has been configured using the above information, the EHR can make requests to decision support services at the appropriate times based on the hooks it supports. To make a request, the EHR prepares a request object containing the contextual information required for the hook, as well as any additional prefetch information.
web	cds-hooks.org	The service responds with a set of cards describing any recommendations or suggestions that should be presented to the user:

web

github.com

web cds-hooks.org Note that this topic is a very high-level approach to using CDS Hooks to support these two use cases. It is not a normative description of any of the CDS Hooks content. Please refer to the CDS Hooks specification itself for more details. At the time of this publication, the CDS Hooks specification has been balloted but is still in the process of being published. Because the links on this page deep-link the CDS Hooks specification, they are still referencing the original CDS Hooks specification. When it is published, the CDS Hooks specification will be located at http://cds-hooks.hl7.org .

web cds-hooks.org The first phase in consuming a CDS Service using CDS Hooks is to configure the integration from the EHR. The CDS Service publishes a set of endpoints to advertise available functionality using the discovery endpoint. For each endpoint, the service declares the hook during which it expects to be invoked, and optionally, any prefetch information that could be provided to the service.

web cds-hooks.org Each hook identifies contextual information that is available within the EHR. For example, the order-sign hook specifies the patient in context, as well as the orders being signed. When invoking the service from this hook, the EHR is expected to provide this contextual information as part of the request.

web cds-hooks.org In addition, the CDS Service may specify additional information using prefetch templates. Each prefetch template is a FHIR query URL, parameterized by the data available in context, and describing information needed by the CDS Service to perform its processing. By providing this information as part of the request, the EHR alleviates the need for the CDS Service to request the additional information.

web cds-hooks.org The second phase is the actual request/response call to the CDS Service. Once the integration has been configured using the above information, the EHR can make requests to decision support services at the appropriate times based on the hooks it supports. To make a request, the EHR prepares a request object containing the contextual information required for the hook, as well as any additional prefetch information.

web cds-hooks.org The service responds with a set of cards describing any recommendations or suggestions that should be presented to the user:

Internal Images

../assets/images/001.svg

tree-filter.png