documentation:vocabulary:principles
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
documentation:vocabulary:principles [2015/01/20 00:59] cgreich created |
documentation:vocabulary:principles [2016/06/20 10:27] (current) cgreich |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | The Standardized Vocabularies are constructed with a few principles in mind. Not every principle can be executed to perfection, but it represents a general motivation and direction of the ongoing improvement and development process: | + | ===== Principles ===== |
| - | * Comprehensive Coverage of all clinical entities in a domain. The Standardized Vocabularies intend to capture every event that is relevant to the patient's clinical experience (e.g. Conditions, Procedures, Exposures to Drug, etc.) and some of the administrative artifacts of the healthcare system (e.g. Visits, Care Sites, etc.). This means that in many cases a single Vocabulary is not sufficient to cover a Domain. For example, RxNorm, which is the source for Ingredients and drug products in the Drug Domain, does not cover products not marketed in the USA, and therefore Concepts from other Vocabularies (ATC, Multilex) have to be used to complement RxNorm in covering the Domain. | + | The Standardized Vocabularies are constructed with a few principles in mind. Not every principle has been executed to perfection, but it represents a general motivation and direction of the ongoing improvement and development process: |
| - | * Only one Standard Concept per clinical entity and the avoidance of duplication. This is easier if the Concepts of a Domain are very precisely defined (e.g. the Drug domain). For Domains where the Concepts have nuanced meanings (e.g. Condition, Procedure) this is a more challenging task. | + | |
| - | * Meaningful and high-quality hierarchy involving all concepts of a domain. This entails the solution of two separate problems: | + | - **Standardization:** Multiple Vocabularies used in observational data are consolidated into a common format. This relieves the researchers from having to understand and handle multiple different formats and life cycle conventions of the originating Vocabularies. |
| + | - **Unique Standard Concepts**: For each Clinical Entity there is only one Concept representing it, called the Standard Concept. Other equivalent or similar Concepts are designated non-Standard and mapped to the Standard ones. | ||
| + | - **Domains:** Each Concept is assigned a Domain. "Dirty" Non-Standard Concepts can also belong to more than one Domain. This also defines in which CDM table a clinical entity should be placed into or looked up in at query time. | ||
| + | - **Comprehensive coverage:** Every event that is relevant to the patient's healthcare experience (e.g. Conditions, Procedures, Exposures to Drug, etc.) and some of the administrative artifacts of the healthcare system (e.g. Visits, Care Sites, etc.) are covered by the Concepts of a Domain. | ||
| + | - **Hierarchy:** Within a Domain all Concepts are organized in a hierarchical structure. This allows to query for all Concepts (e.g. drug products) that are hierarchically subsumed under a higher level Concept (e.g. a drug class). This entails addressing two separate problems: | ||
| * Each Concepts should have one or more classifications (bottom up). | * Each Concepts should have one or more classifications (bottom up). | ||
| * Each Classification should contain all the relevant Concepts (top down). | * Each Classification should contain all the relevant Concepts (top down). | ||
| - | The top-down problem has the additional difficulty in that Classifications are not always generally agreed on. For example, whether diabetic complications are part of the Condition Diabetes or are separate is differently answered by the respective SNOMED and ICD-9 hierarchies. | + | - **Relationships** between Concepts within and across Vocabularies and **Mappings** from non-Standard to Standard Concepts. |
| - | * Life cycle keeping data representation up to date but supporting the processing of deprecated Concepts. This means that for each deprecated Concept a replacement Concept has to be assigned capturing the meaning of the clinical entity. | + | - **Life cycle** keeping data representation up to date but supporting the processing of deprecated and upgraded Concepts. |
| - | * Precise unique Domain assignment for each Standard Concept, and combination of Domains for "dirtier" non-standard Source Concepts. | + | |
| + | It is important to note that these critera have the purpose to serve observational research. In that regard the Standardized Vocabularies differ from large collections with equivalence mappings of concepts such as the [[http://www.nlm.nih.gov/research/umls|UMLS]], which supports indexing and searching of the entire biomedical literature. UMLS resources have been used heavily as a basis for constructing many of the Standardized Vocabulary components, but significant additional efforts have been made to adjust the framework: | ||
| + | |||
| + | * Additional Vocabularies, mostly for metadata purposes, are established. | ||
| + | * Mappings and relationships are being added to achieve comprehensive coverage. If equivalence cannot be achieved, "uphill" relationships from more granular non-standard to higher level Standard Concepts are created. | ||
| + | * A comprehensive domain structure is established and each Concepts was assigned a Domain (or combination of Domains). | ||
| + | * A hierarchical tree within Domains was built representing classifications used in medical science and clinical practice. | ||
| + | |||
| + | However, significant work needs to be done to achieve all the criteria in all of the Domains. Currently, for the complex and non-administrative Domains we can achieve the following compliance: | ||
| + | |||
| + | ^Domain^Standardization^ Unique Concepts ^ Reliable Domains ^ Comprehensive Coverage ^ Hierarchy ^ Mapping ^ | ||
| + | |Drug| x | x | In US, other countries in process | x | x | x | | ||
| + | |Condition| x | x | mostly | x | x | mostly | | ||
| + | |Procedure| x | heavily overlapping | x | x | | x | | ||
| + | |Measurement| x | somewhat | mostly | x | minimal | | | ||
| + | |Device| | | mostly | | | | | ||
| + | |Unit| x | x | x | x | | | | ||
| + | |||
| + | The Life Cycle is implemented for all Concepts, and its rules are described in the CONCEPT table [[documentation:cdm:concept|description]] and in the discussion of the individual vocabularies (if there are specific rules, but this is rare). | ||
| + | |||
documentation/vocabulary/principles.1421715569.txt.gz · Last modified: 2015/01/20 00:59 by cgreich
Page Tools
