-
Notifications
You must be signed in to change notification settings - Fork 75
Vocab. ABMS
Sources are being downloaded from here.
The procedures for transforming Concepts from the source to the OMOP Standard Vocabularies can be found on the OHDSI GitHub {replace xyz with the vocab dir}.
All Concepts are assigned the longest of all available names.
{describe provenance and format of the concept codes}
sample text: All xyz codes are non-Standard which means that they are mapped to the respective Standard concepts defined by the vocabulary team. Technically, they have single (1-to-1) or several (1-to-many) "Maps to" relationships in the concept_relationship_table.
sample text: For each Concept, the Domain is inferred from the SNOMED Concept it is mapped to. If a Source Concept is mapped to more than one target SNOMED Concept, a combination Domain is assigned. If a Concept has no mappings the Domain is inferred from its neighboring codes.
Domain | Notes |
---|---|
Condition | |
Measurement | |
Observation | |
Procedure |
sample text: ICD10 has two Concept Classes: "ICD10 code" and "ICD10 Hierarchy". "ICD10 Hierarchy" Concepts are all highest level 3-character codes. All codes which are subclassifications of them and contain a dot in the code are Concept Class "ICD10 code".
Class | Notes |
---|---|
xyz | |
zyx |
sample text: There are only mapping relationships defined for ICD10.
sample text: ICD10 concepts are non-Standard Concepts and therefore are mapped to Standard Concepts through records in the CONCEPT_RELATIONSHIP table. All such mappings point to SNOMED-based concepts. Most of these SNOMED Concepts are in the Condition Domain, but despite the fact that ICD10 is a "Classification of Disease" some of them get mapped to Procedure, Measurement and Observation Domain Concepts. All mappings are manually maintained by a team of curators.
Most mappings establish one-to-one equivalence between the Concepts. However, some ICD10 Concepts are pre-coordinated (consist of several semantic components), contain negations, declarations about conditions at an unspecified time in the past (e.g. medical history of), declarations about people other than the patient (e.g. family history), lab test findings, mixed mother/child conditions or Observations. All these cases are properly handled as described in the Mapping description.
sample text: ICD10 Concepts are non-Standard Concepts and therefore do not participate in the hierarchy of the CONCEPT_ANCESTOR table.
sample text: All ICD10 concepts are non-Standard. That means they have to be mapped to the corresponding Standard Concepts using the CONCEPT_RELATIONSHIP table ("Maps to" and occasionally "Maps to value" records). Most of them are mapped to single Condition Concepts, generating one-to-one records in the CONDITION_OCCURRENCE table, but some of them create multiple records or mappings to other domains.
Quick access:
- Home
- News
- Introduction
- Glossary
- The Vocabulary Team
- Roadmap
- Release Notes
- Upcoming Changes
- Community Contribution
- General Structure, Download and Use
- Domains
- Vocabularies
- Vocabulary Statistics
- Vocabulary Development Process
- Vocabulary Metadata
- Quality Assurance and Control
- Known Issues in Vocabularies
- Articles
- COVID-19 Vocabulary/ETL Instructions
- Historical Versions