Differences

This shows you the differences between two versions of the page.

--- documentation:vocabulary:background [2015/01/20 00:31] – created cgreich
+++ documentation:vocabulary:background [2024/09/03 07:41] (current) – jcruz
@@ Line 1: / Line 1: @@
 ===== Background and Motivation =====
-The Standardized Vocabularies contains all of the code sets, terminologies, vocabularies, nomenclatures, lexicons, thesauri, ontologies, taxonomies, classifications, abstractions, and other such data that are required for:
+Thank you for visiting the wiki! This page has moved to https://github.com/OHDSI/Vocabulary-v5.0/wiki/Introduction#background-and-motivation.
-  * Generation of the transformed (i.e., standardized) data from the raw dataset into CDM	,
-  * Searching, querying and extraction of the transformed data, and browsing and navigating the hierarchies of classes and abstractions inherent in the transformed data, and
-  * Interpreting the meanings of the data.
-Observational outcome research uses longitudinal patient level clinical data in order to describe and understand the pathogenesis of disease and the effect of other clinical events as well as treatment interventions on the progression of the disease. For this, it uses observational data, i.e. data collected about the patients usually for purposes other than research (primary use): mostly administrative data such as insurance reimbursement claims and Electronic Health or Medical Record (EHR, EMR) data.
-Because the data are collected for primary use, the format and representation follows that primary use. It also introduces artifacts and bias into the data. Observational research however requires a picture of the patient experience as close to the clinical reality as possible. In addition, all source datasets differ from each other in format and content representation, which makes robust, reproducible and automated research a significant challenge. Since healthcare systems differ between countries, the problem becomes even harder for research carried out internationally.
-The solution is the standardization of the data and a standardization of the representation. This allows methods and tools to operate on data of disparate provenance, freeing the analyst from having to dissect the idiosyncrasies of anyone dataset and focusing on the validity of the analytical approach.
-The OMOP CDM and Standardized Vocabularies provide such a framework for systematic research. This framework consists of the following components and mechanisms:
-  * Multiple Vocabularies used in observational data consolidated into a common format. This relieves the researchers from having to understand and handle multiple different formats and life cycle conventions these Vocabularies come with.
-  * Assignment of a Domain for each Concept of the Vocabularies. For each concept, the Standardized Vocabularies define the clinical Domain, and with it the CDM table a clinical entity should be placed into or looked for during queries.
-  * Relationships between Concepts within the Vocabularies and across Vocabularies, e.g. Relationships between Concepts in the Condition Domain as indication to Concepts in the Drug Domain, as well as mapping of equivalent Concept in different Vocabularies to each other.
-  * Hierarchical structure within Concepts of a Domain. This allows to researcher to query for all Concepts (e.g. drug products) that are hierarchically subsumed under a higher level Concept (e.g. a drug class).
-It is important to note that these components are constructed strictly for the purpose of supporting observational research. In that regard the Standardized Vocabularies differ from large collections with equivalence mapping of concepts such as the [[XXX|UMLS]]. 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 the purpose of this resource:
-  * Additional Vocabularies were created, mostly for metadata purposes.
-  * Mappings and relationships were added to achieve comprehensive coverage. If equivalence couldn't be achieved, "uphill" relationships from more granular non-standard to higher level Standard Concepts were created.
-  * 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.
-The availability of very large-scale healthcare databases in electronic form, such as administrative claims and electronic health record data, has opened the possibility to generate systematic and large-scale evidence and insights about the application of healthcare to patients. Amongst them the effectiveness and risks of treatment interventions. However, because of a lack of standardization, clinical terminologies may differ across databases. One approach to fully harvest the value of multiple data sources and assure that the output is comparable is to standardize source codes into a common terminology.
-In the US, diagnosis codes in medical claims are generally processed based on the International Classification of Diseases, Ninth Revision, Clinical Modification (ICD-9-CM) coding system. The Health Insurance Portability and Accountability Act (HIPAA) prescribes adoption rules about how transaction standards for electronic healthcare data interchange for covered entities are regulated, among them the use of ICD-9-CM.[4] From October 2013, ICD-10-CM , the successor to ICD-9-CM, must be used on all HIPAA transactions.[5]  For inpatient hospital procedure coding, the International Classification of Diseases, Tenth Revision, Procedure Coding System (ICD-10-PCS) will be used.[6]