ID
35105
Beschreibung
OMOP Common Data Model (CDM) Observation The OBSERVATION table captures clinical facts about a Person obtained in the context of examination, questioning or a procedure. Any data that cannot be represented by any other domains, such as social and lifestyle facts, medical history, family history, etc. are recorded here. The Observational Medical Outcomes Partnership (OMOP) was a public-private partnership established to inform the appropriate use of observational healthcare databases for studying the effects of medical products. © 2014 Observational Health Data Sciences and Informatics This work is based on work by the Observational Medical Outcomes Partnership (OMOP) and used under license from the FNIH at http://omop.fnih.org/publiclicense. Version updated on 18.02.2019, from https://github.com/OHDSI/CommonDataModel/wiki/NOTE Observations differ from Measurements in that they do not require a standardized test or some other activity to generate clinical fact. Typical observations are medical history, family history, the stated need for certain treatment, social circumstances, lifestyle choices, healthcare utilization patterns, etc. If the generation clinical facts requires a standardized testing such as lab testing or imaging and leads to a standardized result, the data item is recorded in the MEASUREMENT table. If the clinical fact observed determines a sign, symptom, diagnosis of a disease or other medical condition, it is recorded in the CONDITION_OCCURRENCE table. Valid Observation Concepts are not enforced to be from any domain. They still should be Standard Concepts, and they typically belong to the 'Observation' or sometimes 'Measurement' domain. Observations can be stored as attribute value pairs, with the attribute as the Observation Concept and the value representing the clinical fact. This fact can be a Concept (stored in VALUE_AS_CONCEPT), a numerical value (VALUE_AS_NUMBER), a verbatim string (VALUE_AS_STRING), or a datetime (VALUE_AS_DATETIME). Even though Observations do not have an explicit result, the clinical fact can be stated separately from the type of Observation in the VALUE_AS_* fields. For facts represented as Concepts no domain membership is enforced. When storing patient responses to survey questions, each record in the OBSERVATION table represents a single question/response pair and is linked to a specific survey/questionnaire using OBSERVATION.OBSERVATION_EVENT_ID and SURVEY_CONDUCT.SURVEY_CONDUCT_ID. An individual survey question can have multiple responses to a question (e.g. which of these items relate to you, a,b,c,...?). Each response is stored as a separate record in the OBSERVATION table. The question / answer OBSERVATION record is linked to the patient questionnaire used for collecting the data using two new fields in the OBSERVATION table; OBS_EVENT_FIELD_CONCEPT_ID and OBSERVATION_EVENT_ID: OBS_EVENT_FIELD_CONCEPT_ID for any survey related observations contains the concept that refers to the field SURVEY_CONDUCT_ID and OBSERVATION_EVENT_ID contains the actual SURVEY_CONDUCT_ID of the specific survey. This construct can be used for other observation groupings. The OBSERVATION table can also store survey scoring results. Many validated PRO questionnaires have scoring algorithms (many of which proprietary) that return an overall patient score based on the answers provided. Survey scores are identified by their OBSERVATION_CONCEPT_ID and are linked back to the scored survey using the same EVENT_FIELD construct described above. In the name/value pair model, the name (question) is stored as OBSERVATION_CONCEPT_ID and the value (answer) is stored as OBSERVATION_AS_CONCEPT_ID where the answer is categorical and is defined as a concept in the concept table, OBSERVATION_AS_NUMBER where the answer is numeric, OBSERVATION_AS_STRING where the answer is a free text string or OBSERVATION_AS_DATETIME.
Link
http://omop.fnih.org/publiclicense
Stichworte
Versionen (5)
- 04.01.17 04.01.17 -
- 18.02.19 18.02.19 -
- 18.02.19 18.02.19 -
- 26.02.19 26.02.19 -
- 26.02.19 26.02.19 -
Rechteinhaber
Observational Medical Outcomes Partnership (OMOP)
Hochgeladen am
18. Februar 2019
DOI
Für eine Beantragung loggen Sie sich ein.
Lizenz
Creative Commons BY-NC 3.0
Modell Kommentare :
Hier können Sie das Modell kommentieren. Über die Sprechblasen an den Itemgruppen und Items können Sie diese spezifisch kommentieren.
Itemgroup Kommentare für :
Item Kommentare für :
Um Formulare herunterzuladen müssen Sie angemeldet sein. Bitte loggen Sie sich ein oder registrieren Sie sich kostenlos.
OMOP Common Data Model (CDM) Observation
OMOP Common Data Model (CDM) Observation
- StudyEvent: ODM
Ähnliche Modelle
OMOP Common Data Model (CDM) Observation
- StudyEvent: ODM
C2708733 (UMLS CUI-2)
C1955348 (UMLS CUI-3)
C1300638 (UMLS CUI [1,2])
C1300638 (UMLS CUI [1,2])
C0178566 (UMLS CUI [1,2])
C1300638 (UMLS CUI [1,3])
C0011008 (UMLS CUI [1,2])
C0011008 (UMLS CUI [1,2])
C0040223 (UMLS CUI [1,3])
C0332307 (UMLS CUI [1,2])
C0178566 (UMLS CUI [1,3])
C1300638 (UMLS CUI [1,4])
C1522609 (UMLS CUI [1,2])
C1547402 (UMLS CUI [1,2])
C0178566 (UMLS CUI [1,2])
C1300638 (UMLS CUI [1,3])
C0178566 (UMLS CUI [1,2])
C1300638 (UMLS CUI [1,3])
C0178566 (UMLS CUI [1,2])
C1300638 (UMLS CUI [1,3])
C1300638 (UMLS CUI [1,2])
C2745955 (UMLS CUI [1,2])
C1300638 (UMLS CUI [1,3])
C1522508 (UMLS CUI [1,2])
C1300638 (UMLS CUI [1,3])
C0449416 (UMLS CUI [1,2])
C0805701 (UMLS CUI [1,3])
C0600091 (UMLS CUI [1,4])
C0449416 (UMLS CUI [1,2])
C0178566 (UMLS CUI [1,3])
C1300638 (UMLS CUI [1,4])
C0449416 (UMLS CUI [1,2])
C0805701 (UMLS CUI [1,3])
C0449416 (UMLS CUI [1,2])
C0805701 (UMLS CUI [1,3])
C0600091 (UMLS CUI [1,4])
C0441471 (UMLS CUI [1,2])
C1300638 (UMLS CUI [1,3])
C0441471 (UMLS CUI [1,2])
C0178566 (UMLS CUI [1,3])
C1300638 (UMLS CUI [1,4])
C0011008 (UMLS CUI [1,2])
C0040223 (UMLS CUI [1,3])
C1522609 (UMLS CUI [1,4])