Update VISIT_DETAIL.md

Correction - visit_detail_concept_id should be just visit_concept_id; because in the same domain. Otherwise we will have to systematically rename all _concept_id fields in visit_detail into _detail_concept_id; e.g. 

visit_type_concept_id to visit_detail_type_concept_id
admitting_source_concept_id to admitting_detail_source_concept_id

makes it long and difficult in join statements etc
This commit is contained in:
Gowtham Rao 2017-09-18 06:41:58 -04:00 committed by GitHub
parent 2a6bcd0c5e
commit 3b6bcd01f6
1 changed files with 1 additions and 1 deletions

View File

@ -5,7 +5,7 @@ Field|Required|Type|Description
:------------------------|:--------|:-----|:-------------------------------------------------
|visit_detail_id|Yes|integer|A unique identifier for each Person's visit or encounter at a healthcare provider.|
|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.|
|visit_detail_concept_id|Yes|integer|A foreign key that refers to a visit Concept identifier in the Standardized Vocabularies.|
|visit_concept_id|Yes|integer|A foreign key that refers to a visit Concept identifier in the Standardized Vocabularies.|
|visit_start_date|Yes|date|The start date of the visit.|
|visit_start_datetime|No|datetime|The date and time of the visit started.|
|visit_end_date|Yes|date|The end date of the visit. If this is a one-day visit the end date should match the start date.|