- Vocabulary Place of Service belongs to the domain Place of Service and is used to populate place_of_service_concept_id in the care_site table.
- Vocabulary Visit belongs to the domain Visit and is used to populate Visit_concept_id.
- Vocabulary Place of Service is mapped to Visit in both concept_relationship and concept_ancestor table (I dont know how complete this is @Dymshyts ?) Place of Service is a child of Visit
- There is a n:1 relationship between visit_occurrence table and care_site table - so there may not be more than one care_site_id per visit_occurrence_id record. As an extension, there may not be more than one place_of_service_concept_id per visit_occurrence_id.
Would it then be reasonable to add all the conceptās in Place of Service vocabulary from Place of Service domain into Visit domain, as a standard_concept and maintain hierarchical relationship?
I wanted to ask - of the 59 standard and about 487 total conceptās in the Place of Service domain, can we change their domain to visit - so that they may be used in the visit_occurrence table as either visit_concept_id and visit_source_concept_id?
The classification of visitās into inpatient and outpatient is then natural using the concept ancestor table