> 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-specifications/snomed-ct-editorial-guide/readme/authoring/scope/adjudication-for-content-requests.md). # Adjudication for Content Requests There are processes for making decisions about adding or changing content in SNOMED CT. ## Change requests All change requests, whether for new content or for change to existing content, go through a request submission approval process. It involves review by authors to determine that there is: * International applicability * Compliance with Understandable, Reproducible, Useful (URU) principles * No duplication with existing content * No link to existing larger projects, as detailed in a Content Tracker document * No conflict with existing collaboration agreements (e.g. *Logical Observation Identifiers Names and Codes (LOINC)* agreement) {% hint style="warning" %} Legacy concepts, i.e. concepts not in the current draft/work-in-progress version of SNOMED CT, may not follow current guidelines. Requests based on legacy concepts are unacceptable. {% endhint %} ## Appeals, deferrals, and resolution ### Appeals Requests that are rejected may be appealed by the submitter. ### Deferrals Requests may be deferred for a number of reasons including questions about: * How to model the concept; which attributes may be used * Concept meaning * Literature reference missing or inadequate * Use case unclear * Size of required change (attached to a Content Tracker) ### Resolution Resolution of deferrals may result in a decision delay requiring: * A larger project or work item or * Referral, internally, to other groups for decision. This depends on the complexity of the request and understanding of the wider impact. ## Results Results of adjudication are received by email from the Content Request System (CRS). Simpler issues can be resolved expeditiously (e.g. by a ruling from the Chief Terminologist). 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-specifications/snomed-ct-editorial-guide/readme/authoring/scope/adjudication-for-content-requests.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.