VISIT_DETAIL表
VISIT_DETAIL表是一个可选表，用于表示父visit_occurrence表中每条记录的详细信息。对于visit_occurrence表中的每个记录，visit_detail表中可能有0个或更多记录，呈1：n比例，其中n可能为0. visit_detail。表在结构上与visit_occurrence表非常相似，属于与访问类似的域。
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.
| Field | Required | Type | Description |
|---|---|---|---|
| visit_detail_id | Yes | integer | A unique identifier for each Person's visit or encounter at a healthcare provider. |
| 就诊-详情-id | -- | -- | 居民在任何医疗机构就诊行为的唯一标识符。 |
| person_id | Yes | integer | A foreign key identifier to the Person for whom the visit is recorded. The demographic details of that Person are stored in the PERSON table. |
| 居民-id | -- | -- | 外键，指向该表所记录的就诊居民的标识符。该人员的人口统计详细信息存储在PERSON表中。 |
| visit_detail_concept_id | Yes | integer | A foreign key that refers to a visit Concept identifier in the Standardized Vocabularies belonging to the 'Visit' Vocabulary. |
| 就诊-详情-概念-id | -- | -- | 外键，指向标准词汇表中“就诊”词汇表的就诊概念的标识符。 |
| visit_detail_start_date | No | date | The start date of the visit. |
| 就诊-详情-起始-日期 | -- | -- | 就诊的起始时间 |
| visit_detail_start_datetime | Yes | datetime | The date and time of the visit started. |
| 就诊-详情-起始-日期时间 | -- | -- | 就诊的起始日期+时间 |
| visit_detail_end_date | No | date | The end date of the visit. If this is a one-day visit the end date should match the start date. |
| 就诊-详情-截止-日期 | -- | -- | 就诊的结束日期。如果这是一天就诊，则结束日期应与开始日期匹配。 |
| visit_detail_end_datetime | Yes | datetime | The date and time of the visit end. |
| 就诊-详情-截止-日期时间 | -- | -- | 就诊的详细截止日期和时间 |
| visit_detail_type_concept_id | Yes | Integer | A foreign key to the predefined Concept identifier in the Standardized Vocabularies reflecting the type of source data from which the visit record is derived belonging to the 'Visit Type' vocabulary. |
| 就诊-详情-类型-概念-id | -- | -- | 外键，标准词汇表中预定义的概念标识符，反映从中导出访问记录的源数据类型，属于“访问类型”词汇表。 |
| provider_id | No | integer | A foreign key to the provider in the provider table who was associated with the visit. |
| 共享者-id | -- | -- | 外键，指向与就诊关联的贡献者表中的贡献者们。 |
| care_site_id | No | integer | A foreign key to the care site in the care site table that was visited. |
| 医疗机构 | -- | -- | 外键，访问的护理站点表中护理站点。 |
| visit_detail_source_value | No | string(50) | The source code for the visit as it appears in the source data. |
| 就诊-详情-源-值 | -- | -- | 访问源代码在源数据中存储。 |
| visit_detail_source_concept_id | Yes | Integer | A foreign key to a Concept that refers to the code used in the source. |
| 就诊-详情-源-概念-id | -- | -- | 外键，指向源数据使用的编码、代码 |
| admitted_from_source_value | No | Varchar(50) | The source code for the admitting source as it appears in the source data. |
| 允许-从-源-值 | --- | -- | 源数据中允许的、显示的源代码。 |
| admitted_from_concept_id | Yes | Integer | A foreign key to the predefined concept in the 'Place of Service' Vocabulary reflecting the admitting source for a visit. |
| 允许-来自-概念-id | -- | -- | 外键，指向“医疗机构地点”词汇表中预设的概念，反映了就诊的准入来源 |
| discharge_to_source_value | No | Varchar(50) | The source code for the discharge disposition as it appears in the source data. |
| 出院-到-源-值 | -- | -- | 源数据里存储的出院后目的地的源码 |
| discharge_to_concept_id | Yes | Integer | A foreign key to the predefined concept in the 'Place of Service' Vocabulary reflecting the discharge disposition for a visit. |
| 出院-到-概念-值 | -- | -- | 外键，指向“医疗机构地点”词汇表中预置的概念，反映一次就诊后，出院的目的地 |
| preceding_visit_detail_id | No | Integer | A foreign key to the VISIT_DETAIL table of the visit immediately preceding this visit |
| 先前-就诊-详情-id | -- | -- | 外键，指向该次就诊的前1次就诊所对应的VISIT_DETAIL表 |
| visit_detail_parent_id | No | Integer | A foreign key to the VISIT_DETAIL table record to represent the immediate parent visit-detail record. |
| 就诊-详情-父代-id | -- | -- | 外键，VISIT_DETAIL表所记录的，指向上一级父代 visit-detail 记录 |
| visit_occurrence_id | Yes | Integer | A foreign key that refers to the record in the VISIT_OCCURRENCE table. This is a required field, because for every visit_detail is a child of visit_occurrence and cannot exist without a corresponding parent record in visit_occurrence. |
| 就诊-发生-id | -- | -- | 外键，指向VISIT_OCCURRENCE表中的记录。这是一个必填字段，因为每个visit_detail都是visit_occurrence的子代文件，且若在visit_occurrence中没有相应的父记录时则不能存在。 |
共识
所有VISIT_OCCURRENCE表的共识都适用于VISIT_DETAIL表，另外还需注意的请见以下详情：
All conventions used in VISIT_OCCURRENCE apply to VISIT_DETAIL, with some notable exceptions as detailed below
| No. | Convention Description | 共识 |
|---|---|---|
| 1 | 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. | 就诊详情是选填信息，记录每次到医疗机构的就诊详情。对于VISIT_DETAIL中的每条记录，必须有父VISIT_OCCURRENCE记录。 |
| 2 | One record in VISIT_DETAIL can only have one VISIT_OCCURRENCE parent. | VISIT_DETAIL中的一条记录只能有一个父代VISIT_OCCURRENCE。 |
| 3 | A single VISIT_OCCURRENCE record may have many child VISIT_DETAIL records. | 一个VISIT_OCCURRENCE记录可能有许多子VISIT_DETAIL记录。 |
| 4 | 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. | 有效的访问概念属于“访问”域。标准访问概念尚未定义，但将代表VISIT_OCCURRENCE中标准访问概念的详细信息。 |
| 5 | Handling of death: In the case when a patient died during admission (VISIT_DETAIL.DISCHARGE_TO_CONCEPT_ID = 4216643 'Patient died'), a record in the Observation table should be created with OBSERVATION_TYPE_CONCEPT_ID = 44818516 (EHR discharge status 'Expired'). | 死亡处理：如果患者在住院时死亡（VISIT_DETAIL.DISCHARGE_TO_CONCEPT_ID = 4216643'患者死亡'），应创建观察表中的OBSERVATION_TYPE_CONCEPT_ID = 44818516（EHR出院状态'过期'）记录。 |
| 6 | Source Concepts from place of service vocabularies are mapped into these Standard Visit Concepts in the Standardized Vocabularies. | 来自机构地点词汇表的源概念被映射到标准化词汇表中的“标准就诊概念”。 |
| 7 | 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. | 在任何一天，可能会有不止一次就诊。VISIT_OCCURRENCE允许记录一天内进行的多次就诊。VISIT_DETAIL用于仅捕获就诊中的详细信息。 |
| 8 | 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. | 一次就诊可能涉及多个贡献者，在这种情况下，在VISIT_OCCURRENCE中，ETL必须指定如何选择单个PROVIDER_ID或将PROVIDER_ID字段保留为空。VISIT_DETAIL允许ETL为每个VISIT_OCCURRENCE指定多个子记录 - 并且每个子记录可以表示不同的PROVIDER_ID。 |
| 9 | 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. | 一次就诊可能涉及多个医疗机构，这种情况下，在VISIT_OCCURRENCE中，ETL必须指定如何选择单个CARE_SITE_ID或将CARE_SITE_ID字段保留为null。VISIT_DETAIL允许ETL为每次就诊发生表指定多个子记录 - 并且这些子记录中的每一个可以表示不同的CARE_SITE。 |
| 10 | 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. | 就像在VISIT_OCCURRENCE中一样，VISIT_DETAIL中的记录可能根据每个记录的顺序相关联。使用PRECEDING_VISIT_DETAIL_ID表示这些顺序关系。 |
| 11 | Unlike VISIT_OCCURRENCE, VISIT_DETAIL may have nested visits with hierarchical relationships to each other. These relationships are represented using VISIT_DETAIL_PARENT_ID. | 与VISIT_OCCURRENCE不同，VISIT_DETAIL可能存在彼此具有层级嵌套关系的就诊关系。这些关系使用VISIT_DETAIL_PARENT_ID表示。 |
| 12 | 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. | 在“美国索赔数据”中，标题/摘要数据总结了详细说明索赔的整个索赔和行/详细信息，因此详细信息是摘要的子项，对于摘要中的每个记录，都有一个或多个详细记录。即从VISIT_DETAIL到VISIT_OCCURRENCE将至少有一个外键链接。 |
例如：患者的整个住院期可能是VISIT_OCCURRENCE表中的一条记录。这可以有一个或多个详细记录，例如ER，ICU，医疗楼层，康复楼层等。这些就诊细节中的每一个可以具有不同的开始/结束日期 - 时间，不同的concept_id和fact_id。这些将成为VISIT_DETAIL中的独立记录，其中包含指向VISIT_OCCURRENCE的外键链接。
For example: an entire inpatient stay maybe one record in the VISIT_OCCURRENCE table. This may have one or more detail records such as ER, ICU, medical floor, rehabilitation floor etc. Each of these visit details may have different start/end date-times, different concept_ids and fact_ids. These would become separate records in VISIT_DETAIL with a FK link to VISIT_OCCURRENCE.
VISIT_DETAIL内的每条记录可以相互顺序性关联 - > ER到ICU再到住院病房，到康复科，或父子层级关联 - >在ICU住院期间去透析治疗室。
Each record within VISIT_DETAIL may be related to each other, sequentially –> ER leading to ICU leading to medical floor, leading to rehabilitation, or in hierarchical parent-child visit –> a visit for dialysis while in ICU.
请注意，域是“就诊”，它在OMOP CDM中的VISIT_OCCURRENCE和VISIT_DETAIL之间共享使用。VISIT_OCCURRENCE的关键区别是：
- 自引用键：新的外键visit_detail_parent_id允许嵌套就诊关系的的自引用。
- VISIT_DETAIL指向VISIT_OCCURRENCE表中的父记录（visit_occurrence_id）
Note the domain is Visit, and it is shared between VISIT_OCCURRENCE and VISIT_DETAIL in OMOP CDM. The key deviation from VISIT_OCCURRENCE is
- self-referencing key: a new foreign key visit_detail_parent_id allows self referencing for nested visits.
- VISIT_DETAIL points to its parent record in the VISIT_OCCURRENCE table (visit_occurrence_id)
本系列在介绍目前世界上最适用于临床科研+卫生经济学的标准医疗大数据格式（未经严谨考证，但有相关研究发表在专业期刊上），俨然是真实世界研究方案里面最接进成熟的基础建设方案。感兴趣的介绍请移步B站观看视频。
OHDSI——观察性健康医疗数据科学与信息学，是一个世界性的公益型非盈利研究联盟，主要研究全方位医学大数据分析的开源解决方案，旨在通过大规模数据分析和挖掘来提升临床医学数据价值，实现跨学科、跨行业的多方合作。目前，目前，已有来自美国、加拿大、澳大利亚、英国等几十个国家地区的上百个组织机构，高校，医院和公司企业参与了OHDSI全球协作网络，如斯坦福、哈佛、杜克大学医学院，强生、诺华、甲骨文、IBM公司，拥有超过6亿人口的临床数据规模，累计协作研究发表了上百篇论文。
我们在这里邀请国内对相关工作感兴趣、愿共同学习的好学人士参与到中文兴趣小组，互通有无，一起弥补跨行业、跨学科的知识积累。前期主要以对OHDSI在github上的开源工作进行翻译、交流、学习为主，并会对医疗大数据、医学统计学、生物信息学等学科知识建立学习互助、互督的机制。有兴趣的请看文档，微信群二维码在内：OHDSI中文兴趣小组共识&OHDSI介绍
OHDSI秉持开源、开放的宗旨，加快全球医学数据研究的步伐，本文内容原创来自Github（https://github.com/OHDSI/CommonDataModel/wiki），若有利益冲突，请在本页面留言，真-侵删。
