Specify how to handle required fields when the data is missing, or falls outside of listed enumerations

[brendagutman]

Can we define universal mappings for 'Missing', 'Asked but Unknown', 'Unknown', 'Asked but Other', 'Outside of enumerations'?

Should harmonizers remove all rows where the field cannot be populated?

Family_member.relationship - Required field

Demographics.DownSyndromeStatus - Required field
Will this data always exist in the source data?

Bonus question:
Demographics.sex - Required field
Are these the correct enums? Where are we at with 'Unknown' and 'Other'?

[RobertJCarroll]

Some enumerations do have unknowns baked in as you can do enumeration inheritance.

In some cases, not populating the row is appropriate, eg, the FamilyRelationship with no relationship specified is not informative. The information is already present via FamilyMember.

Re DS Status- that is strictly required for INCLUDE typically, but it is a field that needs to be taken out into the "INCLUDE specific" section. We could consider unknown there, but mainly for non-INCLUDE sources in the INCLUDE model.

[RobertJCarroll]

Re "other": We really want to avoid it in almost every circumstance as it breaks every existing "other" if/when you change the enumeration.