Page History
...
| Advanced Tables - Table Plus | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The best place to start learning about SNOMED CT or to refresh existing knowledge. An overview of a range of topics related to the terminology. A An informative practical introduction to SNOMED CT focused primarily on the needs of vendors and developers of EHRs and other related applications in healthcare information technology. B The Technical Implementation Guide (TIG) provides a general overview of technical topics related to SNOMED CT implementation. It also provides an entry point to individual guides on more specific topics.
B The National Release Center Guide (NRC Guide) offers a practical starting point for IHTSDO Member countries. It provides guidance on NRC responsibilities and the relationships between NRCs, IHTSDO, and implementers and users within a Member country. To learn more about SNOMED CT please refer instead to the SNOMED CT Starter Guide. D Detailed information about SNOMED CT content development. SNOMED CT CT, hierarchies, defining relationships and content model. F The specification for the SNOMED CT to ICD-10 Maps and Guidance onimplementationof this specification.
G The glossary of terms used in these and other documents about SNOMED CT and IHTSDO. G This document describes a diagrammatic notation for representing the definition of a concept, an expression, or relation between expressions within SNOMED CT. See also 'SNOMED CT Diagramming Guideline Templates' on the Tooling Documentation tab of the Document Library. H This document provides a specification for the format and usage of SNOMED CT URIs. Such a URI might identify "A clinical idea to which a unique Concept Identifier has been assigned"1. However, it does not specify orstandardiseany aspect of the representation of these things. Appropriate representations may vary greatly depending on use-case requirements and servicesutilisingthe URIs specified here are free to make their own choices. H Revised (May 2015) specification of the SNOMED CT Compositional Grammar used for expressions and definitions. The replaces the specification in the current edition of the Technical Implementation Guides H The first part of this guide is concerned with searching the content of SNOMED CT to find concepts that represent particular clinical ideas. The second part of the guide is concerned with ways to use SNOMED CT to support entry of relevant clinical information in electronic health records. I Published (September 2015) specification of SNOMED CT Expression Constraints usedforrepresent constraints on the content and structure of an expression. Also used to represent anintensionalsubset of SNOMED CT concepts. This extends, formalized and replaces earlier informal constraint representations such as those documented in HL7 TermInfo Release 1. W Published (March 2013) a guide that explains the value of migrations to SNOMED CT Release Format 2 (RF2) from the 2002 release format (RF1). For additional information on migration from RF1 to RF2 see section 9.2.1 of the Technical Implementation Guide. X The specification of the old SNOMED CT release format and guidance on its use. The specification is published for those still using the old format. ** Note RF1 is no longer being maintained or developed as it was replaced by RF2 in 2012 ** J This document provides draft advice on how to make effective combined use of SNOMED CT and LOINC in ways that recognize the scope and strengths of the two terminology resources. The guidance also considers ways to deliver added-value by using the links between SNOMED CT and LOINC developed as part of the cooperative work. H | Machine Readable Concept Model | The SNOMED CT Machine Readable Concept Model (MRCM) represents the SNOMED CT concept model rules in a form that can be read and tested by a computer. This specification defines the format used by SNOMED International's MRCM. This format uses the SNOMED CT Reference Set mechanism to provide a file structure with inbuilt versioning, and the Expression Constraint Language to representintensionalSNOMED CT subsets referred to by the concept model rules. This allows distribution of the MRCM usingstandardRF2 reference set files and interpretation of the rules using tools that support the SNOMED CT Expression Constraint Language. | F | The Decision Support with SNOMED CT guide reviews the approaches, toolsandtechniques used to implement clinical decision support with SNOMED CT, and shares developing practice in this area. It is anticipated that this guide will benefit members, vendorsandusers of SNOMED CT by promoting a greater awareness of how SNOMED CT has been and can be used to enhance clinical decision support implementations. F | Practical Guide to Reference Sets | The SNOMED CT Practical Guide to ReferenceSets startsby identifying practical use cases and the requirements that must be met to address them. It then explains how different types of reference sets can be used to meet those requirements. It also provides advice on different approaches to creating, editing, maintaining and using reference sets to support effective localization and customization of SNOMED CT. | F | Extensions Practical Guide | The Extensions Practical Guide presents the purpose, processandprinciples of creating, distributing and managing SNOMED CT extensions. Extension producers should be familiar with this guidance to ensure the quality and integrity of the SNOMED CT editions that they publish. This guide has been developed to assist National Release Centers and other extension producers to develop extensions based on recommended principles
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Overview
Content Tools
Apps