SNOMED CT Maturity Framework
Implementation Level | Data Capture | Data Retrieval |
Level 5 | Advanced Use |
Awesome Icon |
---|
color | #008080 |
---|
size | 30pt |
---|
icon | fa- |
---|
|
|
barsLevel 0: PLANS TO USE SNOMED CT SNOMED CT is not used yet, but there are plans to do so. Clinical information is stored as free text or using other code systems. | | SNOMED CT is recorded directly in the health records, and used as an ontology. Support for expressions, expression constraints (ECL) and the Machine Readable Concept Model (MRCM) may be provided. | SNOMED CT codes or expressions are stored directly in health records based on clinician input. Searching or navigation uses Description Logic reasoning or Natural Language Processing. May also use Clinical Decision Support with Description Logic or Artificial Intelligence. | Querying is performed over SNOMED CT codes and expressions using computable languages, such as the Expression Constraint Language (ECL). Reasoning over SNOMED CT codes and expressions using Description Logic. |
Level 4 | Semantic Network |
Awesome Icon |
---|
color | #008080 |
---|
size | 30pt |
---|
icon | fa- |
---|
|
|
exchange Level 1: MAPPING TO SNOMED CT not recorded Awesome Icon |
---|
color | #008080 |
---|
size | 30pt |
---|
icon | fa-list-ul |
---|
|
| Level 2: SIMPLE CODE SYSTEM SNOMED CT is directly recorded in the clinical records. It's used as a flat list of codes. |
clinical records. It's used indirectly, using a mapping mechanism.health record, and used as a semantic network of relationships with simple ECL queries. All defining relationships may be traversed to support various system functions. | SNOMED CT codes are stored directly in health records based on clinician input. Searching or navigation using defining relationship is provided. Clinical decision support may also be provided, with rules based on defining relationships. | SNOMED CT codes are aggregated or queried based on automated subsets or queries that may use any defining relationship (including both 'is a' and attribute relationships). |
Level 3 | Hierarchy |
Awesome Icon |
---|
color | #008080 |
---|
size | 30pt |
---|
icon | fa-sitemap |
---|
|
|
Level 3: HIERARCHY | SNOMED CT is recorded directly |
recorded clinical records. It's health record, and used as a hierarchy of codes to support various system functions. |
Awesome Icon |
---|
color | #008080 |
---|
size | 30pt |
---|
icon | fa-connectdevelop |
---|
|
| Level 4: SEMANTIC NETWORK SNOMED CT is directly recorded in the clinical records. It's used as a semantic network of relationships with simple ECL queries. |
SNOMED CT codes are stored directly in health record based on clinician input, with searching or navigation using hierarchy. Clinical decision support may be provided, with rules based on hierarchical relationships. | SNOMED CT codes are aggregated or queried based on automated subsets or queries that use SNOMED CT's hierarchical relationships. |
Level 2 | Simple Code System |
Awesome Icon |
---|
color | #008080 |
---|
size | 30pt |
---|
icon | fa- |
---|
|
|
cogs Level 5: ADVANCED USE | SNOMED CT is recorded directly |
recorded clinical records. It's used as an ontology with full MRCM and ECL support, and the ability to create, classify and query new clinical meanings.SNOMED CT Maturity Levels:
Level 0SNOMED CT is not used yet, but there are plans to do so. Clinical information is stored as free text or using other code systems, like local value lists or classification codes. Data retrieval is primarily one record at a time. Some reporting available using selected codes and simple groupers from other code systems.
Level 1
SNOMED CT is not directly recorded in the clinical records. It's used indirectly, using a mapping mechanism. The system uses other code system as a controlled vocabulary, and each code is mapped to SNOMED CT on the background. The diversity of SNOMED CT codes available through mapping is limited by the mapping quality. A great effort is required to maintain the maps, adding new codes depending on user needs and updating to new SNOMED releases. SNOMED CT can be used in a limited way to support data retrieval.
Level 2
SNOMED CT is directly recorded in the clinical records, based on clinician input. It's used as a flat list of codes imported into the clinical system. Support health records, and used as a flat list of codes. Support for translated terms or multiple synonyms may also be provided. | SNOMED CT codes are stored directly in health record based on clinician input, using flat value lists. Support may be provided for translated terms, multiple synonyms or |
Clinical Decision Support clinical decision support based on manually defined subsets. |
Data retrieval is supported by | SNOMED CT codes are aggregated or queried using manually defined subsets. May support string-based searches over multiple (or localized) synonyms. |
Level |
31 | Mapping to SNOMED CT |
Awesome Icon |
---|
color | #008080 |
---|
size | 30pt |
---|
icon | fa-exchange |
---|
|
| SNOMED CT |
codes stored is not recorded directly in the health record |
based on clinician input, with searching or navigation using hierarchy The hierarchical structure of , the inferred relationships, are imported into the system. Clinical Decision Support may be provided, with rules based on hierarchical relationships. Data retrieval is supported by SNOMED CT codes aggregated or queried based on automated subsets or queries that use SNOMED CT’s hierarchical relationships.Level 4
SNOMED CT codes stored directly in health records based on clinician input. Searching or navigation using defining relationships is provided. All the inferred relationships are imported into the system. Clinical Decision Support may also be provided, with rules based on defining relationships. Data retrieval is supported by SNOMED CT codes aggregated or queried based on automated subsets or queries that may use any defining relationship (including both ‘is a’ and attribute relationships).
Level 5
SNOMED CT codes or expressions stored directly in health records based on clinician input. Searching or navigation uses Description Logic reasoning or Natural Language Processing. The SNOMED CT release is loaded into an advanced terminology server. May also use Clinical Decision Support with Description Logic or Artificial Intelligence. Data retrieval is supported by reasoning over SNOMED CT codes and expressions using Description Logic. Querying over SNOMED CT codes and expressions using computable languages, such as the Expression Constraint Language (ECL)is used indirectly by mapping to SNOMED CT. | Another code system is used to enter the clinical data, with mapping to SNOMED CT in the background. | Another code system is retrieved in the clinical record, with mapping used to display corresponding SNOMED CT codes or terms. |
Level 0 | Plans to Use SNOMED CT |
Awesome Icon |
---|
color | #008080 |
---|
size | 30pt |
---|
icon | fa-bars |
---|
|
| SNOMED CT is not yet used within the health record, but there are plans to do so. Clinical information is currently stored as free text or using local or vendor specific code systems. | Information is captured using simple value lists, text fields or radio buttons. | Data retrieval is primarily one record at a time. Some reporting is available using selected codes from a simple code system. |