> 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-extension-guide/5-key-steps/5.6-distribution/5.6.3-implementation-guidance.md). # Implementation Guidance Extension producers should ensure that the consumers of their extension understand how to use and implement the extension. It is therefore recommended that extension producers provide specific guidance on the: * Purpose of the extension * Scope and content of the extension * Module dependencies within the extension * Usage of the extension Additionally, it is important that consumers of the extension can trust the quality of the extension and understand how to validate its contents. It is therefore also recommended that guidance on validating the extension is provided. {% hint style="info" %} Please note that this guide focuses on guidance for extension producers. Specific implementation guidance for extension consumers should be provided by the extension producer themselves, to supplement the general implementation guidance provided by SNOMED International (see ). {% endhint %} 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-extension-guide/5-key-steps/5.6-distribution/5.6.3-implementation-guidance.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.