Mappings for patient, family history, social history and location

[janhaviel]

Added mappings for the patient, family history, social history and location tables from the ACEP data dictionary, corresponding to tickets DAN-55, DAN-56, DAN-57, DAN-58

[pverma12394]

• social_history_observed_value and family_history_observed_value will map to obersvation_concept_id alongwith observation_source_value. Reason: a source value is mapped to a concept ID, whereas source codes are mapped to source_concept_ids. "A source code may not always be a concept ID" , therefore all source codes/concept IDs are mapped to source_concept_id attributes

[pverma12394]

• Type codes in the acep will not map to obersvation_concept_id for the same reason as above. They are mapped to observation_source_concept_id only

[janhaviel]

That makes sense thank you! We got the rationale behind using the observed_value to derive concept_id but we were wondering if we can implement a logic here that if the social_history_type_code or family_history_type_code does not have a corresponding concept_code in the concept table then we should derive the observation_concept_id from the social_history_observed_value and family_history_observed_value? Or would that cause any issues?

[pverma12394]

If the code is available and the choice of standard vocabulary is same as source, then we use the code to fetch the concept ID, else if code is unavailable or missing then we use the value to map to the corresponding concept ID. That logic is part of the vocabulary mapping process which will be discussed later.

@ishitasati11 FYI