Authoring Level 2 Competencies
| 站点: | SNOMED CT E-Learning Platform |
| 课程: | Course Information |
| 图书: | Authoring Level 2 Competencies |
| 打印: | 访客用户 |
| 日期: | 2025年11月25日 星期二 11:07 |
1. Introduction
The authoring level 2 certification recognizes your competence in performing advanced SNOMED CT authoring tasks. The authoring level 2 competencies represent:
- The set of knowledge and skills that are considered necessary to achieve an advanced level of authoring competence
- The minimum requirements needed to pass the authoring level 2 certification exam
- The context in which the questions and tasks for the authoring level 2 course and certification exam have been developed.
The key competency categories are:
|
1. Design Principles of SNOMED CT |
SNOMED CT design to meet the fundamental principles of modern medical terminology and why this is important |
|
2. SNOMED CT Content |
SNOMED CT content coverage, structure and use case |
|
3. Content Request Process |
SNOMED CT content development, request submission and request submission management process |
|
4. SNOMED CT Concept Model |
Purpose and features of the SNOMED CT concept model and Machine Readable Concept Model |
|
5. Editorial Guidance |
SNOMED International Editorial Guide and other guides |
|
6. SNOMED CT Authoring |
Required tasks in creating and revising SNOMED CT concepts |
|
7. Terminology Processes |
Authoring Process, Quality Assurance, Release Process, Release Validation, ECL and Translation |
Further details of the competencies belonging to each category are provided in the subsequent sections of this Ebook.
The level of competency is based on the Revised Bloom Taxonomy (6 levels)
1) Remember – Retrieve relevant knowledge from long-term memory
2) Understand – Determine the meaning of instructional messages, including oral, written, and graphic communication
3) Apply – Carry out or use a procedure in a given situation
4) Analyze – Break material into its constituent parts and detect how the parts relate to one another and to an overall structure or purpose
5) Evaluate – Make judgments based on criteria and standards
6) Create – Put elements together to form a novel, coherent whole or make an original product
Please Note: The Authoring Level 2 Course and Certification exam only require the authoring of content in the Procedure, Clinical finding and Situation with explicit context hierarchies.
2. Design Principles of SNOMED CT
|
1. Design Principles of SNOMED CT: SNOMED CT design and why it is important |
|||
|
Competency Item |
Area of Skill |
Competency |
Level |
|
1.1 |
Controlled Medical Vocabulary Principles |
Identify the key principles of "desiderata for controlled medical vocabularies" and how they are met by the design of SNOMED CT |
Understand |
|
1.2 |
SNOMED CT Scope |
Consider what content would be allowed in SNOMED International and its extensions when authoring content. |
Evaluate |
|
1.3 |
SNOMED CT Extensions Creation |
Appreciate the technical aspects required for creating SNOMED CT extension. Be able to explain the difference between an Edition and an Extension, and how SNOMED CT releases are versioned. Have knowledge of the use and importance of Modules and Module Dependencies. Be aware of the required maintenance processes of Extensions to ensure content integrity and traceability across releases. Comprehend the principles for content promotion and demotion. |
Understand |
|
1.4 |
SNOMED CT Logical Design |
Understand the logical design model of SNOMED CT components and the types of information that are associated with each of the components. |
Understand |
|
1.5 |
Description Logic |
Have an appreciation of DL features used in SNOMED CT, such as General Concept Inclusion (GCI) axioms, and how these effect content classification and hierarchy structure. |
Understand |
3. SNOMED CT Content
|
2. SNOMED CT Content: SNOMED CT content coverage, structure and use case |
|||
|
Competency Item |
Area of Skill |
Competency |
Level |
|
2.1 |
SNOMED CT Hierarchies |
Understand how SNOMED CT content is organized, and the definitions and use cases for all the different hierarchies. Have a reasonable knowledge of the content that exists within all the SNOMED CT hierarchies. Be aware of the need for creation of new attribute value concepts to enable concepts to be sufficiently defined and support correct subsumption |
Understand |
|
2.2 |
SNOMED CT Content - Selection |
Search for and decide on the most appropriate SNOMED CT content to be used when performing authoring tasks within the authoring platform. Be able to use Expression Constraint Language to help evaluate content. |
Evaluate |
|
2.3 |
SNOMED CT Content - Evaluation |
Evaluate the accuracy of existing content using knowledge of SNOMED CT content |
Evaluate |
|
2.4 |
SNOMED CT Model Component Hierarchy |
Choose the correct content from the SNOMED CT Model Component hierarchy when authoring |
Apply |
|
2.5 |
Release File Versioning |
Identify the component attributes used for versioning in Release Format 2 (RF2) |
Understand |
|
2.6 |
SNOMED CT Extensions Content |
Appreciate the importance of SNOMED CT extensions, their key content principles, and their dependencies |
Understand |
|
2.7 |
Content Development Tools |
Be aware of the essential tools that authors and developers of SNOMED CT Editions may use as part of their work as an author or producer of SNOMED CT extensions and editions |
Remember |
4. Content Request Process
|
3. Content Request Process: SNOMED CT content development and request submission process |
|||
|
Competency Item |
Area of Skill |
Competency |
Level |
|
3.1 |
Content Development |
Identify how SNOMED CT content is developed, including stakeholders involved, triggers for content change, how SNOMED International manages change processes and all the types of content changes. Have knowledge of the key factors to consider when deciding how to handle content requests in content areas that are still under development. Be aware of how complex content development projects are managed |
Understand |
|
3.2 |
Request Submission |
Act on the different types of content requests, and determine when and where requests should be submitted |
Analyse |
|
3.3 |
Request Considerations – Information Gathering |
Search and critique sources of truth on the meaning of the concept. Evaluate the quality and sufficiency of sources using criteria (CRAAP test) specifically to determine details necessary for complex concept modeling. |
Evaluate |
|
3.4 |
Request Considerations – Concept Construction |
Construct acceptable descriptions and decide on correct hierarchical placement |
Create |
|
3.5 |
Request Submission Management |
Determine the best way to manage content requests and communicate with stakeholders |
Apply |
|
3.6 |
Request Submission Analysis |
Demonstrate ability to accurately evaluate justification, analyse request and decide acceptability for inclusion in SNOMED CT |
Evaluate |
5. SNOMED CT Concept Model
|
4. SNOMED CT Concept Model: Purpose and features of the SNOMED CT concept model and Machine Readable Concept Model |
|||
|
Competency Item |
Area of Skill |
Competency |
Level |
|
4.1 |
Concept Model Purpose |
Recognise the purpose of the SNOMED CT concept model |
Remember |
|
4.2 |
Concept model |
Understand the SNOMED CT concept model key features : Root and top-level concepts, subtype and attribute relationships, concept and axiom definitions, groups, domains and ranges. Understand the concept model for all the hierarchies. |
Understand |
|
4.3 |
Description Logic |
Appreciate why Description Logic is important for authoring SNOMED CT content, understand the open world view and how the Unique Name Assumption is reflected in SNOMED CT. Understand the description logic features used in SNOMED CT and why they are applied. |
Understand |
|
4.4 |
SNOMED CT diagrams |
Interpret concept definitions using SNOMED CT diagrams of stated, authoring and inferred views. Understand how GCI are represented. |
Apply |
|
4.5 |
Machine Readable Concept Model |
Understand the purpose of the Machine Readable Concept Model and how it is used in the authoring process. Apply the rules defined in the MRCM (Attribute Domain, Attribute Range, Cardinality, and Grouping) to construct new concept definitions and expressions accurately. Evaluate existing content for MRCM compliance, ensuring all concepts adhere to the current concept model. This includes validating the correct use of cardinality constraints (e.g., In Group Cardinality) to achieve consistent classification results |
Apply |
6. Editorial Guidance
|
5. Editorial Guidance: SNOMED International Editorial Guide and other guides |
|||
|
Competency Item |
Area of Skill |
Competency |
Level |
|
5.1 |
SNOMED International Editorial Guide |
Understand the structure and importance of the Editorial Guide in the process of authoring. Be able to search the guide effectively |
Apply |
|
5.2 |
International naming conventions and editorial guidance |
Comprehend and use SNOMED International Editorial Guide and Pre-coordination Pattern for the following hierarchies Procedure, Body Structure, Clinical Finding, Situation with Explicit Context. |
Apply |
|
5.3 |
National and Local Extension Editorial Guides |
Recognise the need for national and local extension editorial guides and how they may differ from the SNOMED International Editorial Guide, and used to support request submission decisions. Understand the key principles involved in planning and creating editorial guidance. |
Understand |
|
5.4 |
Templates |
Appreciate how modeling templates are a crucial tool for consistency and quality assurance in SNOMED CT authoring |
Understand |
7. SNOMED CT Authoring
|
6. SNOMED CT Authoring: Required tasks in creating and revising SNOMED CT concepts |
|||
|
Competency Item |
Area of Skill |
Competency |
Level |
|
6.1 |
Authoring Platform |
Effectively use the SNOMED CT Training Authoring Platform to perform authoring tasks |
Apply |
|
6.2 |
Platform Rules |
Ability to abide by Authoring Platform Terms of Usage |
Apply |
|
6.3 |
Authoring Process |
Create or modify SNOMED CT content to a high standard in the following hierarchies: Procedure, Clinical Finding and Situation with Explicit Context |
Create |
|
6.4 |
Editorial Guides |
Find and apply all relevant guidance when authoring content including naming conventions and concept modelling |
Apply |
|
6.5 |
Descriptions |
Develop the most appropriate descriptions (Fully specified names and synonyms) to capture the precise concept meaning. Select the correct hierarchical semantic tag. Avoid creating any description that is not semantic equivalent to the FSN |
Create |
|
6.6 |
Case significance |
Decide on the correct case significance for each description |
Apply |
|
6.7 |
Reference Set preference |
Determine the language reference set preference settings |
Evaluate |
|
6.8 |
Proximal Primitive Parent Modelling |
Choose the most appropriate proximal primitive supertype(s) including where necessary intermediate proximal primitive concept(s). Create accurate attribute-value pair relationships to express the meaning of the concept. |
Apply |
|
6.9 |
Intermediate Primitive Parent |
Know what an intermediate primitive concept is, and manage the challenges of finding and using proximal intermediate parents when appropriate. Author concepts that have intermediate primitive parents and interpret whether after classification the resulting hierarchical position is correct. Correctly follow guidance on whether to choose a GCI concept as a parent or a higher level primitive concept |
Evaluate |
|
6.10 |
Stated, Inferred and Authoring Form View |
Understand the differences between the stated, inferred and authoring form views in the SNOMED International Authoring Platform and use views in the creation and analysis of classified concepts |
Analyse |
|
6.11 |
Relationship grouping |
Apply the correct relationship groups to a concept in accordance with Editorial Guidance |
Apply |
|
6.12 |
Definition status |
Evaluate whether an axiom definition meets the “necessary and sufficient” condition to be sufficiently defined |
Evaluate |
|
6.13 |
Classification |
Apply description logic knowledge to evaluate classification results and any subsequent modelling changes |
Apply |
|
6.14 |
Description Changes |
Change or inactivate descriptions by applying the principles for allowed description changes, including the rules that apply for the different description types e.g. not semantically equivalent synonyms |
Apply |
|
6.15 |
Logical Definitions Changes |
Perform definitional changes to concepts after evaluating the principles around changing the logical definition of a concept including what changes are permitted to SNOMED CT relationships, what types of changes may be made to a relationship group, and the implications surrounding changes to a concept's definition status |
Apply |
|
6.16 |
Concept Inactivation |
Ascertain when an existing concept in SNOMED CT should be inactivated and select the correct inactivation reason. Correctly inactivate a concept using awareness of reference set mechanisms that ensure persistence of meaning when a concept is inactivated. Be able to accurately perform complex inactivations, where the inactivated concept is the target of historical associations and/or an attribute value for another concept and/or has subtypes. |
Apply |
|
6.17 |
Concept reactivation |
Determine the necessary steps and modeling requirements (primitive parent(s), defining attributes) to reactivate a previously inactivated released concept |
Evaluate |
|
6.18 |
Attribute Value Concepts |
Assess the impact on other content of adding a concept that may be used as the value of an attribute in the definition of other concept relationships |
Evaluate |
|
6.19 |
Concept review |
Review the accuracy of new and existing concept descriptions and relationships, as well as evaluating their hierarchical position |
Evaluate |
8. Terminology Processes
|
7. Terminology Processes: Authoring Process, Quality Assurance, Release Process, Release Validation, ECL and Translation |
|||
|
Competency Item |
Area of Skill |
Competency |
Level |
|
7.1 |
Collaborative Authoring Techniques |
Understand collaborative task-based authoring principles, including managing tasks and projects, rebasing to synchronize content, and resolving merge conflicts. |
Understand |
|
7.2 |
Utilizing ECL for Authoring Processes |
Create and execute Expression Constraint Language (ECL) queries to facilitate authoring tasks including content querying, content quality assurance and content adherence to editorial guidelines. Ability to use and apply the examples in the Expression Constraint Language - Specification and Guide to formulate accurate ECL queries. |
Create |
|
7.3 |
Release Process |
Understand key principles in regard to preparing a new version of SNOMED CT for release |
Understand |
|
7.4 |
Release Validation |
Understand key principles in regard to release validation |
Understand |
|
7.5 |
Translation |
Understand how translation of SNOMED CT is performed using concept-based translation principles |
Understand |
|
7.6 |
Quality Assurance |
Understand the key principles applied to quality assure SNOMED CT |
Understand |