> 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/snap2snomed-user-guide/how-to-.../3-mapping-with-snap2snomed/3.2-projects.md).

# Projects

A project is a collection of one or map versions that have the same source and target code systems (but not necessarily the same code system versions).

For example a single project could contain 2 maps: *ACME codes to SNOMED map v1 (source: ACME code system v1.0, target: SNOMED CT International version 20210131)* and *ACME codes to SNOMED map v2 (source: ACME code system v1.0, target SNOMED CT International version 202107031).*

When creating a new map, a project is automatically created. When a new version of an existing map is created within the tool, it will be placed into the same project as the original version that has been copied.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=snap2snomed+User+Guide&#x26;entry.670899847=3.2%20Projects" 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/snap2snomed-user-guide/how-to-.../3-mapping-with-snap2snomed/3.2-projects.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.