SNOMED CT Foundation Cour
Module C Summary
Module C –Prentations
▪FC01) Introduction to Reference Sets
▪FC02) Using SNOMED CT Configurable Features ▪FC03) Translation and Language Preferences
▪FC04) Introduction to Mapping
▪FC05) Introduction to SNOMED CT Expressions
▪FC06) Introduction to SNOMED CT Implementation
FC01) Introduction to Reference Sets
▪A reference t
▪Is an RF2 file format for distributing a SNOMED CT subt
▪Contains a t of references to SNOMED CT components
▪May also include additional information about each component
▪Different types of refts are ud for different purpos ▪Simple refts reprent subts (‘referencedComponentId’)
▪Language refts indicate dialect preferences (‘acceptabilityId’)
▪Simple map refts reprent maps between SNOMED CT concepts and codes in other code systems (‘mapTarget’)
▪Ordered refts prioritize items in a list (‘order’, ‘linkedToId’)
▪Attribute value refts associate a value with components (‘valueId’) –e.g. Concept inactivation indicator
▪Association refts reprent a t of unordered associations
我是学霸(‘targetComponentId’) –e.g. Historical association refts
▪Module dependency refts reprent module dependencies
▪Reference t descriptor specifies format of all refts in a relea
FC02) Using SNOMED CT Configurable Features
▪Solving problems using configurable features
▪Identification of customization problem
▪Identification of needed configurable features柠檬皮可以吃吗
▪Design configurable features and add to extensions
▪Implementation
五行命格查询▪Example solutions
▪Content extensions
▪Adding concepts, descriptions and relationship files
▪Derivative only and mapping extensions
▪Adding reference ts
–For example, subts, maps, language refts
▪Combination extensions
▪Adding core components plus reference ts
–For example, descriptions + language refts, concepts + maps
FC03) Translation and Language Preferences
▪SNOMED CT
▪Is concept oriented
▪Enables translated terms to be associated with a shared concept ▪Allows indication of different language and dialect preferences
POPs
▪Descriptions in different languages reprent translations ▪Language reference ts reprent language preferences ▪Refer to the subt of descriptions that are acceptable and
preferred for u in a given language, dialect or context
▪Translation of SNOMED CT
▪Is a multi-disciplinary task
▪Is undertaken by IHTSDO Members that require SNOMED CT in
their national language
▪Must be concept-bad (not literal)
▪Should follow best practice guidance bad on terminology
principles and past experience
FC04) Introduction to Mapping
▪Mapping purpos
▪To meet reporting requirements (‘Collect once, u many times’)▪To support interoperability, data migration, data integration
▪Types of maps
▪SNOMED CT to statistical classification
▪Other standard or local code systems to/from SNOMED CT
▪Links to knowledge references and decision support tools
▪Steps in developing and using maps
▪Requirements, develop, distribute, u, review, revi & maintain ▪Maps may be reprented using reference ts ▪Simple map, Complex map, Extended map, Expression map
美丽心灵影评▪Available Maps for SNOMED CT
▪ICD-10, ICD-10-CM, ICD-9-CM, ICD-O3, ICPC2, LOINC, ICNP
FC05) Introduction to SNOMED CT Expressions
▪SNOMED CT expression
女的性欲强▪A structured combination of one or more concept identifiers ud
to reprent a clinical meaning
▪Ud in health records, messages, concept definitions, links to
knowledge resources, links to other code systems
▪Precoordinated and postcoordinated expressions
有关春节的句子▪Advantages and disadvantages of postcoordination
▪SNOMED CT Compositional Grammar
▪Focus concept, refinement, attribute (name and value)
Example: “Pain in the left thumb” can be reprented as
53057004|hand pain|:
363698007|finding site|= (76505004|thumb structure|:
272741003|laterality|=7771000|left|)
▪IHTSDO Diagramming Guidelines
▪Alternatives to postcoordinated expressions
FC06) Introduction to SNOMED CT Implementation ▪SNOMED CT reprents clinical information meaningfully when implemented as part of a well-designed health record ▪Types of SNOMED CT applications
▪SNOMED CT implementation stages and starting points
▪A stepwi approach to implementation is possible
▪SNOMED CT can be ud as:
▪A code system to store clinical information
▪An interface terminology to capture and display clinical information ▪An indexing system to retrieve c雪花牛肉的做法
linical information
▪A common terminology to communicate in a meaningful way
▪A dictionary to query, analy, report & link to knowledge resources ▪An extensible foundation to reprent new types of clinical data
▪Key Determinants of success
▪National u and implementation examples
Links to further information
▪SNOMED CT Starter Guide (snomed/sg.pdf)▪Chapters 7, 8, 10, 11, 12
▪Technical Implementation Guide (snomed/tig.pdf)▪Sections 3, 4.1.3, 4.3.3, 4.3.4, 5.6, 7.4, 7.6.3, 7.9, 8.4.3, 10
▪SNOMED CT Editorial Guide
▪Chapter 7 (Terming and Naming Conventions)
▪Diagramming Guidelines (snomed/diaguide.pdf)
▪IHTSDO Glossary (snomed/gl)
▪SNOMED CT in Action (snomedinaction)
▪IHTSDO Website
▪SNOMED CT ICD-10 Mapping Specification
▪LOINC and SNOMED CT Implementation Guides
▪Building the Business Ca for SNOMED CT
