> 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/how-to.../creating-requests.md).

# Creating Requests

## What mode should I use?

| Task                                                       | Simple | Batch Import |
| ---------------------------------------------------------- | ------ | ------------ |
| Modify, retire, or, create a single Concept                | **x**  | **x**        |
| Make more than one change to an existing Concept           |        |              |
| **n/a**                                                    | **x**  |              |
| Retire more than one more component to an existing Concept |        |              |
| **n/a**                                                    |        |              |

## What is Simple mode used for?

In **Simple Mode** , a user can create a request to perform a single action on one concept:

* create a new Concept
* Add a new Description to an existing concept
* Add a new Relationship to an existing concept
* Modify an existing Description of an existing concept
* Change a Relationship of an existing concept
* Retire a Description of an existing concept
* Retire Relationship of an existing concept
* Change or Retire an existing Concept
* Other - all requests not covered by the above types

## What is Batch mode used for?

In **Batch Mode** , a user can create a request to perform a multiple (typically) related actions

## Form Fields

In each of the Simple and Direct modes, there are certain fields which are mandatory and need to be completed on each request:

| Field | Description                                                        | Mandatory | Notes |
| ----- | ------------------------------------------------------------------ | --------- | ----- |
| Topic | From the dropdown, choose the relevant area/domain for the request | Y         |       |

Summary| Provide a short summary which will help staff identify and triage the request| Y| *Please note this field has a 255 character limit*\
Proposed Use Case| Provide justification on why the content should be added or changed| Y|

Reference| Provide references which can be verified to confirm the need to add or change the content| Y|

Local SNOMED CT Code| Add the local valid SNOMED CT identifier of the content to be added if one exists|\
|

Local Code| Add any other local code identifiers for your own reference|\
|

Definition| Precise meaning of the requested content addition or change|\
|

Notes| Any extra notes which will help the triage of the request|\
|

Namespace| Add the namespace of the content, if applicable|\
|

UMLS CUI| Add the UMLS Concept Unique Identifier if one exists|\
|

Originating Organization| Choose the organization from the drop down that is requesting the change or addition| Y| *International CRS only*\
Collaboration Agreement| If relevant, select the collaboration agreement under which the request is being made|\
\| *International CRS only*

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Content+Request+Guide&#x26;entry.670899847=Creating%20Requests" 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 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/crs-guide/how-to.../creating-requests.md?ask=<question>&goal=<endgoal>
```

`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.