> 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/loinc-feature-transformation.md). # LOINC Feature Transformation LOINC Concepts feature a number of logical properties - beyond their text descriptions and parts - that required some creative way to surface in a SNOMED CT format. Two examples of these are the ORD/OBS flag (which indicates if a LOINC Term should be used in the context of an Order, and Observation, or Both), and a status of "Discouraged" which indicates that a LOINC Term is still active, but its use should be avoided. Both of these flags exist as columns in the published LOINC distribution csv file and the method for exposing them in a SNOMED CT format is described in the following pages. --- # 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/implementation-guides/loinc-implementation-guide/content-development/loinc-feature-transformation.md?ask=&goal= ``` `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.