> 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/crs-guide/snomed-ct-content-request-service.md).

# How do I obtain a CRS Account?

**What types of Content Requests are supported?**

Before making any request, please read the guidance on submitting content -

[Version 15.0 Customer Guidance for Requesting Changes to SNOMED CT 20240723.pdf](https://github.com/SNOMED-Documents/snomed-crs-guide/blob/main/attachments/12780558/265619216.pdf)

The new CRS tool features a variety of templates and two request entry modes to appeal to most users. These Include:

* **Create a new Concept(s)**

A request for a new concept must take into account existing content and align with the existing Editorial Guidance

* **Add New Synonym(s)**

A new synonym may be added to an existing concept if the request aligns with existing Editorial Guidance and has a clear justification.

* **Add or Modify Parent(s)**

A new parent may be added to an existing concept (or changed) if the request aligns with existing Editorial Guidance and has a clear justification.

* **Add or Modify Description(s)**

A new description may be added to an existing concept (or changed) if the request aligns with existing Editorial Guidance and has a clear justification.

* **Inactivate Concept(s), Description(s), or Relationship(s)**

Concepts or their components may be inactivated if the request aligns with existing Editorial Guidance and has a clear justification.

* **Modify and Create New Relationship(s)**

New relationships or modification to existing concepts may be made if the request aligns with existing Editorial Guidance and has a clear justification.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Content+Request+Guide&#x26;entry.670899847=How%20do%20I%20obtain%20a%20CRS%20Account%3F" class="button primary">Provide Feedback</a>


---

# 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-user-guides/crs-guide/snomed-ct-content-request-service.md?ask=<question>&goal=<user_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.
