> For the complete documentation index, see [llms.txt](https://docs.snomed.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-clinical-decision-support-guide/appendix-a-decision-support-case-studies.md).
# Appendix A - Decision Support Case Studies
As discussed in this guide, SNOMED CT is increasingly being used in clinical decision support (CDS) systems to support healthcare providers in making well informed clinical decisions.
This appendix presents two sets of case studies, which demonstrate the use (or planned use) of SNOMED CT in clinical decision support systems.
* [Organizational Case Studies](/snomed-ct-practical-guides/snomed-ct-clinical-decision-support-guide/appendix-a-decision-support-case-studies/organizational-case-studies.md) describes a range of organizations that use SNOMED CT for clinical decision support;
* [Vendor Case Studies](/snomed-ct-practical-guides/snomed-ct-clinical-decision-support-guide/appendix-a-decision-support-case-studies/vendor-case-studies.md) describes a number of commercial products that use SNOMED CT to enable clinical decision support.
Provide Feedback
---
# 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://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-clinical-decision-support-guide/appendix-a-decision-support-case-studies.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.