> 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-user-guides/simplex-user-guide/faqs/what-are-my-responsibilities-after-publishing-using-simplex.md). # What are my responsibilities after publishing using Simplex? ## User Support The organisation publishing a SNOMED CT Edition using Simplex must offer the first line support for the release that they publish. The organisation name and a contact email must be provided during the release process to be included in the release package readme file. The support effort can be minimized using pre-written responses and signposting to existing relevant support resources. You should expect there to be general questions about how SNOMED CT should be used in the relevant country or region and perhaps some technical questions. The simplest way to respond to these questions is to direct people to a web page. A page should be created to provide any country or region-specific information. For more general questions people can be referred to the [SNOMED CT Document Library](https://docs.snomed.org), which includes the starter guide and RF2 specification. For very specific questions the publishing organisation can contact the International Implementation Support Team for assistance . ## Content Updates A SNOMED CT Edition published from Simplex contains both your created extension content and the International Edition. A new version of the SNOMED CT Edition should be published at least once a year including an up-to-date version of the International Edition. This ensures that downstream users can benefit from the latest developments in the International Edition, even if your extension content has not changed. ## Feedback In addition to the above, it is good practice to provide a feedback mechanism, or a method for users to propose changes or additions to the content. This could be as simple as providing an email address for feedback or utilizing more dedicated request submission services. Establishing a clear and accessible process for feedback helps ensure the content remains relevant and meets user needs. 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-user-guides/simplex-user-guide/faqs/what-are-my-responsibilities-after-publishing-using-simplex.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.