What you’re suggesting @Christian_Reich is that we’ll make them non-Standard and not mapped, correct?
And the VISIT_OCCURRENCE records with 0 visit_concept_id are not better than the Observation records with 0 observation_concept_id.
Another option could be an assignment of the Visit Domain to these poor concepts, but:
- Then ETL needs to create the Visit records relying only on the source concept Domain which is not happening usually, as far as I know,
- It’s hard to keep track of the Domains of the source concepts - it’s done in chunks and script-wise. If the concept undergoes a manual review, this mapping to the Visit record would be a means of distinction.
BTW, how would we accommodate the mapping to the table/fields to the wide mapping table design?