> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/logicnets-software-component-details/healthcare-integration-interoperability-suite/logicnets-cds-hooks-framework-ln-cds.md). # LogicNets CDS Hooks Framework (LN-CDS) ### License: Per LogicNets Installation Notes: 1. Available through Enterprise License options 2. Optionally licensed on a per web services transaction basis 3. Supports use of Informatics Mapping with LN-INF 4. Serves as an alternative to the Web Services Framework when the CDS Hooks integration methodology is required ### LN-CDS Description The LogicNets CDS Hooks Framework is specifically designed to allow healthcare organizations to automate advanced clinical decision support (CDS) through tight integration with the patient record and medical workflow using HL7’s recommended CDS Hooks protocols and methodology. The framework presents at runtime a standard CDS Hooks API that allows EHR systems to invoke the service, authenticate securely and pass patient data necessary to automate a CDS consultation through the Base system or the Use Case Frameworks. It also allows clinical pathways modeled as interactive processes in LogicNets to be navigated in a “silent” mode using data received from the EHR to provide the routing input for navigating the pathways. Having navigated to an endpoint, the system generates a results and history package which it returns through the API to the invoking application. If sufficient data is not available to navigate modeled logic to an endpoint in silent mode, the framework includes in its history package the URL for the clinical pathways package and the specific session that was opened. The invoking program can then re-connect to the original session to display the live CDS pathway and allow the user to interactively provide the information necessary to reach a conclusion and generate results. ### Services and Deployment Considerations The CDS Hooks Framework is delivered as a controlled release and requires LogicNets Design and Deployment Services for delivery and deployment. Design and custom configurations are required in all cases to meet and properly process the specific attributes of the digital content made available through the API. These services are scoped and delivered based on analysis of application and content requirements and require development and acceptance by customer of a formal SoW LogicNets offers training services (LN-TS) for interacting with the CDS Hooks API which can be adjusted based on the user’s familiarity with Web Services and the CDS Hooks protocol. PG-HE3-250103 --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://community-test.logicnets.com/release-9/logicnets-software-component-details/healthcare-integration-interoperability-suite/logicnets-cds-hooks-framework-ln-cds.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.