documentation:vocabulary:principles
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| documentation:vocabulary:principles [2016/06/18 22:49] – cgreich | documentation:vocabulary:principles [2024/09/03 07:40] (current) – jcruz | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Principles ===== | ===== Principles ===== | ||
| - | 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: | + | Thank you for visiting |
| - | + | ||
| - | - **Standardization: | + | |
| - | - **Unique Standard Concepts**: For each Clinical Entity, there is only one Concepts representing it, called the Standard Concept. Other equivalent or similar Concepts are designated non-Standard and mapped to the Standard ones. | + | |
| - | - **Domains: | + | |
| - | - **Comprehensive coverage:** The Standardized Vocabularies intend to capture every event that is relevant to the patient' | + | |
| - | - **Hierarchy: | + | |
| - | - **Relationships** between Concepts within and acros Vocabularies and **Mappings** from non-Standard to Standard Concepts. | + | |
| - | - **Life cycle** keeping data representation up to date but supporting | + | |
| - | + | ||
| - | It is important to note that these critera are followed strictly for the purpose of observational research. In that regard the Standardized Vocabularies differ from large collections with equivalence mapping of concepts such as the [[http://www.nlm.nih.gov/research/umls|UMLS]], | + | |
| - | * Additional Vocabularies were created, mostly for metadata purposes. | + | |
| - | * Mappings and relationships were added to achieve comprehensive coverage. If equivalence cannot be achieved, " | + | |
| - | * A comprehensive domain structure was 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. This entails the solution of two separate problems: | + | |
| - | * Each Concepts should have one or more classifications (bottom up). | + | |
| - | * Each Classification should contain all the relevant Concepts (top down). | + | |
| - | + | ||
| - | 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| | + | |
| - | |Condition| | + | |
| - | |Procedure| | + | |
| - | |Measurement| | + | |
| - | |Device| | | mostly | + | |
| - | |Unit| | + | |
| - | + | ||
| - | The Life Cycle is implemented for all Concepts, and its rules are described | + | |
documentation/vocabulary/principles.1466290174.txt.gz · Last modified: by cgreich
