> 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-extension-guide/4-logical-design/4.4-editions/4.4.2-edition-uri-examples.md). # Edition URI Examples The table below lists a number of national and international SNOMED CT editions.
SNOMED CT EditionIdentifying Module IDEdition URI
International Edition900000000000207008http://snomed.info/sct/900000000000207008
International Spanish Edition449081005http://snomed.info/sct/449081005
Argentinian Edition11000221109http://snomed.info/sct/11000221109
Australian Edition
(with drug extension)32506021000036107http://snomed.info/sct/32506021000036107[
](http://snomed.info/sct/32506021000036107)
Austrian Edition11000234105http://snomed.info/sct/11000234105
Belgian Edition11000172109http://snomed.info/sct/11000172109
Canadian Edition20611000087101http://snomed.info/sct/20611000087101
Danish Edition554471000005108http://snomed.info/sct/554471000005108
Estonian Edition11000181102http://snomed.info/sct/11000181102
Finnish Edition11000229106http://snomed.info/sct/11000229106
German Edition11000274103http://snomed.info/sct/11000274103
Indian Edition1121000189102http://snomed.info/sct/1121000189102
Irish Edition11000220105http://snomed.info/sct/11000220105
Netherlands Edition11000146104http://snomed.info/sct/11000146104
New Zealand Edition21000210109http://snomed.info/sct/21000210109
Norwegian Edition51000202101http://snomed.info/sct/51000202101
Republic of Korea Edition
(South Korea)11000267109http://snomed.info/sct/11000267109
Spanish National Edition900000001000122104http://snomed.info/sct/900000001000122104
Swedish Edition45991000052106http://snomed.info/sct/45991000052106
Swiss Edition2011000195101http://snomed.info/sct/2011000195101
UK Edition83821000000107http://snomed.info/sct/83821000000107
UK Clinical Edition999000021000000109http://snomed.info/sct/999000021000000109
Uruguay Edition5631000179106http://snomed.info/sct/5631000179106
US Edition731000124108http://snomed.info/sct/731000124108
US Edition
(with ICD-10-CM maps)5991000124107http://snomed.info/sct/5991000124107
Edition URIs also exist for other code systems which have been expressed in a SNOMED CT format:
SNOMED CT EditionIdentifying Module IDEdition URI
LOINC Ontology11010000107http://snomed.info/sct/11010000107
NPU Extension to SNOMED CT11003000102http://snomed.info/sct/11003000102
NUVA Extension to SNOMED CT11002000107http://snomed.info/sct/11002000107
To request updates to this table, please click on the *Feedback* button below. For more information about the SNOMED CT URI Standard, please refer to [URI Standard](https://docs.snomed.org/snomed-ct-specifications/snomed-ct-uri-standard/). Provide Feedback --- # 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-extension-guide/4-logical-design/4.4-editions/4.4.2-edition-uri-examples.md?ask=&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.