> 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/implementation-guides/loinc-implementation-guide/content-development/4.2-template-based-content-creation.md).

# Template Based Content Creation

LOINC Terms are expressed as SNOMED CT concepts by following a [transformation algorithm detailed in pseudocode](https://docs.google.com/document/d/1rz2s3ga2dpdwI1WVfcQMuRXWi5RgpJOIdicgOz16Yzg). This has been implemented as a number of Java classes, freely available in [this package in the SNOMED International GitHub Script Library project](https://github.com/IHTSDO/script-library/tree/develop/src/main/java/org/ihtsdo/termserver/scripting/pipeline/loinc).

## Overview <a href="#id-4.2templatebasedcontentcreation-overview" id="id-4.2templatebasedcontentcreation-overview"></a>

The processing algorithm follows these high level steps

1. The Java class loads the Loinc.csv and Part.csv file from the LOINC release
2. A part detail file is also supplied, which specifies part identifiers ("LP") for each part used in each LOINC Term
3. The process works through the part detail file, selecting a template based on the 'Property' part of each LOINC Term
4. Each part is mapped to a SNOMED CT Attribute where:
   1. The Part Type maps to a SNOMED Attribute type as specified in the template and
   2. The Part Number maps to a SNOMED Attribute value as specified via the Part/Attribute Map (maintained in the Snap2Snomed tool)
5. The terms for each concept are then completed, using the preferred terms of the attribute values that have been modelled.
6. The entire set of modelled concepts is the compared against the LOINC Extension in the SI Authoring Platform
7. A delta archive is produced which details changes required from the previous state of the content.

In addition, LOINC Panels are created as primitive concepts, where the individual tests in each panel are available as transformed SNOMED CT concepts.

See [LOINC Presentation](https://docs.google.com/presentation/d/1NvcH06JWgC2ss_A_TQDz9SzQzVR2RNWgBGjG5uARGpw/edit#slide=id.g2871ae07855_0_0)

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=LOINC+Implementation+Guide&#x26;entry.670899847=Template%20Based%20Content%20Creation" 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/implementation-guides/loinc-implementation-guide/content-development/4.2-template-based-content-creation.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.