> For the complete documentation index, see [llms.txt](https://docs.b2ihealthcare.com/snow-owl-authoring-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2ihealthcare.com/snow-owl-authoring-platform/local-code-systems/authoring/creating-local-code-systems.md).

# Creating Local Code Systems

## Creating a Local Code System

To create a new Local Code System, click on the hyperlink in the **Local Code Systems View**, or use the **`New Local Code System...`** ![](https://snowowl.atlassian.net/wiki/download/thumbnails/1198358541/worddave8c1c045badd67b9514e0d3236733d46.png?version=1\&modificationDate=1600711866116\&cacheVersion=1\&api=v2\&width=16) button in the toolbar.&#x20;

{% hint style="info" %}
The hyperlink in the **Local Code Systems View** is only available if no Local Codes are present in the navigator.
{% endhint %}

Specify the properties for your Local Code System. Defining Name and Short name is mandatory.

| Property        | Description                                                                                                                                   |
| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| **ID**          | Enter an ID for the code system, this will be used in the navigator.                                                                          |
| **OID**         | Enter the object identifier for this code system. For more information about OIDs, please see the [HL7 OID Registry](http://www.hl7.org/oid). |
| **URL**         | FHIR-compatible HTTP url for the Code System                                                                                                  |
| **Title**       | Enter the full name of your code system.                                                                                                      |
| **Contact**     | Enter the contact information of the person who maintains this code system.                                                                   |
| **Description** | Enter information describing the code system.                                                                                                 |
| **Copyright**   | Enter copyright if there is one for the Local Code System.                                                                                    |

<figure><img src="/files/AgS0IMC1UmTnrSegTJkv" alt=""><figcaption><p>Specifying properties for Local Code System</p></figcaption></figure>

Click **`Finish`** to proceed. The new code system's editor opens automatically providing the means for additional properties of the Local Code System to be created.&#x20;

{% hint style="info" %}
All created Local Code Systems will appear in the **Code Systems View** as well and can be versioned separately.
{% endhint %}


---

# 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.b2ihealthcare.com/snow-owl-authoring-platform/local-code-systems/authoring/creating-local-code-systems.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.
