> 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-practical-guides/snomed-ct-mapping-guide/developing-use-case-and-requirements/5.3.3-personnel.md).

# Personnel

Mapping requires a multidisciplinary group of people to:

{% stepper %}
{% step %}
**Develop the map**
{% endstep %}

{% step %}
**Undertake the actual mapping**
{% endstep %}

{% step %}
**Verify content**
{% endstep %}

{% step %}
**Test**
{% endstep %}

{% step %}
**Document**
{% endstep %}

{% step %}
**Release**
{% endstep %}
{% endstepper %}

A wide range of expertise is required for the development of a map including:

| Expertise                          | Details                                                                                                                                                                                                                                |
| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Clinical subject matter expertise  | Clinical expertise of the discipline and the way that the result of the map will be used in clinical practice (including workflow). Provide decisions on the clinical safety and appropriateness of the results of each individual map |
| Source code system expertise       | Expertise and understanding of the source scope, coverage, purpose, content and structure                                                                                                                                              |
| Target code system expertise       | Expertise and understanding of the target scope, coverage, purpose, content and structure                                                                                                                                              |
| Technical implementation expertise | Expertise and understanding of the implementations where the source data originates, the target data will be used and the automated processes used to transform the data from source to target                                         |
| Administrative expertise           | Management of the process and project, ensuring repeatability, quality, risk management and consistency                                                                                                                                |

## Requirements for mappers (and reviewers)

Personnel doing the mapping (mappers) should:

* understand and be able to apply the structure, content and relationships for the source and target code systems
* understand the purpose of the map
* understand the way the map will be implemented
* understand the processes associated with new releases of the source and target code systems

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Mapping+Guide&#x26;entry.670899847=Personnel" 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-practical-guides/snomed-ct-mapping-guide/developing-use-case-and-requirements/5.3.3-personnel.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.