- Created by David Markwell, last modified by Peter G. Williams on 2022-Feb-03
The SNOMED CT Release File Specification formally defines the formats in which SNOMED CT is provided to licensees (Affiliates). For information about SNOMED CT licensing and availability of release files please refer to the Member Licensing and Distribution Service(MLDS) (http://snomed.org/licensing).
Web browsable version: http://snomed.org/rfs
SNOMED CT Document Library: http://snomed.org/doc
© Copyright 2024 International Health Terminology Standards Development Organisation, all rights reserved. This document is a publication of International Health Terminology Standards Development Organisation, trading as SNOMED International. SNOMED International owns and maintains SNOMED CT®. Any modification of this document (including without limitation the removal or modification of this notice) is prohibited without the express written permission of SNOMED International. This document may be subject to updates. Always use the latest version of this document published by SNOMED International. This can be viewed online and downloaded by following the links on the front page or cover of this document. SNOMED®, SNOMED CT® and IHTSDO® are registered trademarks of International Health Terminology Standards Development Organisation. SNOMED CT® licensing information is available at http://snomed.org/licensing. For more information about SNOMED International and SNOMED International Membership, please refer to http://www.snomed.org or contact us at info@snomed.org. |
Latest PDF Version for Download: | Note This PDF document was generated from the web version on . Any changes made to the web pages since this date will not appear in the PDF. For information about recent changes please see Recent Updates. |
Contents
1. Introduction
2 SNOMED CT Logical Model
- 2.1 High Level Logical Model of SNOMED CT
- 2.2 Representation of the Logical Model
- 2.3 Concept Definitions
3 Release Types, Packages and Files
- 3.1 Common Features of All Release Files
- 3.2 Release Types
- 3.3 Naming Conventions for Release Packages and Files
- 3.4 Release Package Contents
4 Component Release Files Specification
5 Reference Set Release Files Specification
- 5.1 General Features of Reference Sets
- 5.2 Reference Set Types
- 5.2.1 Content Reference Sets
- 4.2.2. Ordered Component Reference Set
- 5.2.1.1 Simple Reference Set
- 5.2.1.3 Attribute Value Reference Set
- 5.2.1.4 Association Reference Set
- 5.2.1.5 Ordered Association Reference Set
- 5.2.1.6 DEPRECATED: Annotation Reference Set
- 5.2.1.7 Query Specification Reference Set
- 5.2.1.8 Ordered Reference Set
- 5.2.1.9 OWL Expression Reference Set
- 5.2.2 Language Reference Sets
- 5.2.3 Map Reference Sets
- 5.2.3.1 Simple Map from SNOMED CT Reference Set
- 5.2.3.2 Simple Map to SNOMED CT Reference Set
- 5.2.3.3 Complex and Extended Map from SNOMED CT Reference Sets
- 5.2.3.4 Map to SNOMED CT with Correlation and Origin Reference Set
- 5.2.3.5 Code to Expression Reference Set
- 5.2.3.6 Simple map with correlation from SNOMED CT type reference set
- 5.2.3.7 Simple map with correlation to SNOMED CT type reference set
- 5.2.3.8 Simple map with correlation from SNOMED CT to SNOMED CT type reference set
- 5.2.4 Metadata Reference Sets
- 5.2.4.1 Reference Set Descriptor
- 5.2.4.2 Module Dependency Reference Set
- 5.2.4.3 Description Format Reference Set
- 5.2.4.4 MRCM Domain Reference Set
- 5.2.4.5 MRCM Attribute Domain Reference Set
- 5.2.4.6 MRCM Attribute Range Reference Set
- 5.2.4.7 MRCM Module Scope Reference Set
- 5.2.4.8 Component Annotation String Value Reference Set
- 5.2.4.9 Member Annotation String Value Reference Set
- 5.2.1 Content Reference Sets
6 SNOMED CT Identifiers
- 6.1 SCTID Data Type
- 6.2 SCTID Representation
- 6.3 SCTID Constraints
- 6.4 Check-digit
- 6.5 Partition Identifier
- 6.6 Namespace-Identifier
- 6.7 Item-Identifier Digits
- 6.8 Example SNOMED CT identifiers
- 6.9 The Namespace Hierarchy
Appendix A: Notes on Release File Changes
- Representation of the Logical Model - Before July 2018
- Notes on modifierId
- RF1 Compatibility and Conversion Tools
Appendix B. Specification Reference Information
Appendix C. Unicode UTF-8 encoding
Appendix D: Concept Definition Illustrations
Appendix E: Concept Enumerations
- E.1 Concept Enumerations for moduleId
- E.2 Concept Enumerations for definintionStatusId
- E.3 Concept Enumerations for Description typeId
- E.4 Concept Enumerations for caseSignificanceId
- E.5 Concept Enumerations for characteristicTypeId
- E.6 Concept Enumerations for modifierId
- E.7 Concept Enumerations for Relationship typeId
- E.8 Concept Enumerations for Reference Set Attribute Values
Previous Versions
Recent Updates
Feedback