ID
35325
Beschrijving
OMOP Common Data Model (CDM) Visit detail The VISIT_DETAIL table is an optional table used to represents details of each record in the parent visit_occurrence table. For every record in visit_occurrence table there may be 0 or more records in the visit_detail table with a 1:n relationship where n may be 0. The visit_detail table is structurally very similar to visit_occurrence table and belongs to the similar domain as the visit. OMOP Common Data Model Version 6.0 Specifications 11October2018. 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. Version updated on 28.02.2019, from https://github.com/OHDSI/CommonDataModel/wiki/VISIT_DETAIL All conventions used in VISIT_OCCURRENCE apply to VISIT_DETAIL, with some notable exceptions as detailed below: A Visit Detail is an optional detail record for each Visit Occurrence to a healthcare facility. For every record in VISIT_DETAIL there has to be a parent VISIT_OCCURRENCE record. One record in VISIT_DETAIL can only have one VISIT_OCCURRENCE parent. A single VISIT_OCCURRENCE record may have many child VISIT_DETAIL records. Valid Visit Concepts belong to the 'Visit' domain. Standard Visit Concepts are yet to be defined, but will represent a detail of the Standard Visit Concept in VISIT_OCCURRENCE. Handling of death: In the case when a patient died during admission, a record in the Observation table should be created. Source Concepts from place of service vocabularies are mapped into these Standard Visit Concepts in the Standardized Vocabularies. On any one day, there could be more than one visit. VISIT_OCCURRENCE allows for more than one visit within a single day. VISIT_DETAIL is to be used to only capture details within the visit. One visit may involve multiple Providers, in which case, in VISIT_OCCURRENCE, the ETL must specify how a single PROVIDER_ID is selected or leave the PROVIDER_ID field null. VISIT_DETAIL allows for the ETL to specify multiple child records per VISIT_OCCURRENCE - and each of these child records may represent different PROVIDER_IDs. One visit may involve multiple Care Sites, in which case, in VISIT_OCCURRENCE, the ETL must specify how a single CARE_SITE_ID is selected or leave the CARE_SITE_ID field null. VISIT_DETAIL allows for the ETL to specify multiple child records per visit occurrence - and each of these child records may represent different CARE_SITEs. Just like in VISIT_OCCURRENCE, records in VISIT_DETAIL may be sequentially related to each. These sequential relations are represented using PRECEDING_VISIT_DETAIL_ID. Unlike VISIT_OCCURRENCE, VISIT_DETAIL may have nested visits with hierarchical relationships to each other. These relationships are represented using VISIT_DETAIL_PARENT_ID. In US claims data Header/summary data that summarizes the entire claim and Line/detail that details a claim, detail is thus a child of the summary, and for every record in summary there is one or more records in detail. i.e. there will be at least one foreign key link from VISIT_DETAIL to VISIT_OCCURRENCE. For more information, see https://github.com/OHDSI/CommonDataModel/wiki/VISIT_DETAIL
Link
https://github.com/OHDSI/CommonDataModel/wiki/VISIT_DETAIL
Trefwoorden
Versies (1)
- 28-02-19 28-02-19 -
Houder van rechten
Observational Medical Outcomes Partnership (OMOP)
Geüploaded op
28 februari 2019
DOI
Voor een aanvraag inloggen.
Licentie
Creative Commons BY-NC 3.0
Model Commentaren :
Hier kunt u commentaar leveren op het model. U kunt de tekstballonnen bij de itemgroepen en items gebruiken om er specifiek commentaar op te geven.
Itemgroep Commentaren voor :
Item Commentaren voor :
U moet ingelogd zijn om formulieren te downloaden. AUB inloggen of schrijf u gratis in.
OMOP Common Data Model (CDM)
Similar models
Visit detail
- StudyEvent: ODM
C1522508 (UMLS CUI [1,2])
C1300638 (UMLS CUI [1,3])
C1522508 (UMLS CUI [1,2])
C0178566 (UMLS CUI [1,3])
C1300638 (UMLS CUI [1,4])
C0545082 (UMLS CUI [1,2])
C1522508 (UMLS CUI [1,3])
C0545082 (UMLS CUI [1,2])
C1522508 (UMLS CUI [1,3])
C1301880 (UMLS CUI [2,1])
C0545082 (UMLS CUI [2,2])
C1522508 (UMLS CUI [2,3])
C0545082 (UMLS CUI [1,2])
C1522508 (UMLS CUI [1,3])
C0545082 (UMLS CUI [1,2])
C1522508 (UMLS CUI [1,3])
C1522314 (UMLS CUI [2,1])
C0545082 (UMLS CUI [2,2])
C1522508 (UMLS CUI [2,3])
C1522508 (UMLS CUI [1,2])
C0332307 (UMLS CUI [1,3])
C0178566 (UMLS CUI [1,4])
C1300638 (UMLS CUI [1,5])
C1300638 (UMLS CUI [1,2])
C1300638 (UMLS CUI [1,2])
C1522508 (UMLS CUI [1,2])
C0449416 (UMLS CUI [1,3])
C1522609 (UMLS CUI [1,4])
C1522508 (UMLS CUI [1,2])
C0449416 (UMLS CUI [1,3])
C0178566 (UMLS CUI [1,4])
C1300638 (UMLS CUI [1,5])
C0600091 (UMLS CUI [1,2])
C0030673 (UMLS CUI [1,3])
C1300638 (UMLS CUI [1,2])
C0030673 (UMLS CUI [1,3])
C0600091 (UMLS CUI [1,2])
C1550390 (UMLS CUI [1,3])
C1300638 (UMLS CUI [1,2])
C1550390 (UMLS CUI [1,3])
C0205156 (UMLS CUI [1,2])
C1522508 (UMLS CUI [1,3])
C1300638 (UMLS CUI [1,4])
C1522508 (UMLS CUI [1,2])
C1300638 (UMLS CUI [1,3])
C2745955 (UMLS CUI [1,2])
C1300638 (UMLS CUI [1,3])