diff --git a/StandardizedClinicalDataTables/VISIT_OCCURRENCE.md b/StandardizedClinicalDataTables/VISIT_OCCURRENCE.md index f211678..e1e7a6f 100644 --- a/StandardizedClinicalDataTables/VISIT_OCCURRENCE.md +++ b/StandardizedClinicalDataTables/VISIT_OCCURRENCE.md @@ -26,8 +26,7 @@ No.|Convention Description :--------|:------------------------------------ | 1 | A Visit Occurrence is recorded for each engagement of a patient with the healthcare system. It reflects the constellation of such engagement, not an actual concrete healthcare institution.| | 2 | Valid Visit Concepts belong to the 'Visit' domain.| -| 3 | Standard Visit Concepts are defined hierarchically, rolling up into 12 top concepts: - Note that there is a combined "ER and Inpatient Visit" because it is close to impossible to separate the two in many EHR system. | +| 3 | Standard Visit Concepts are defined hierarchically, rolling up into 12 top concepts:
Note that there is a combined "ER and Inpatient Visit" because it is close to impossible to separate the two in many EHR system. | | 4 | Handling of death: Visits are not used to indicate a patient's death. If the source data contains death information in a visit context the date should be derived (admission or discharge) and placed into the death_datetime field of the PERSON table. For details, see [there](https://github.com/OHDSI/CommonDataModel/wiki/VISIT_OCCURRENCE/_edit).| | 5 | Source Concepts from a number of vocabularies are mapped into Standard Visit Concepts. Visit Concepts form a hierarchy. Therefore, the most detailed Visit Concept should be picked or mapped to during ETL. It is no longer necessary to infer a top Concept from the hierarchy. | | 6 | At any one day, there could be more than one visit. |