Gender fields are out of sync across CDM and should include nonbinary/non-binary

[lee0c]

As there are forms of legal ID with 'X' gender markers, the CDM should allow for 'nonbinary' or 'non-binary' as a gender option to align correctly.

I have documented all of the different files which contain gender data that I can find. I would love to PR changes to these files, but want to double check that a) I have all the relevant files and b) that this PR would be accepted.

Here's the files and which options they allow for gender. Ideally, this would be standardized across all files, but I think that might be a lost cause as some of these have options which are direct alternatives to others.

File/line	Male	Female	Non-binary	Other	Unknown	Unidentified	Choose not to identify	Prefer not to say	Item
applicationCommon/Contact	X	X
customerInsights/CustomerProfile	X	X				X	X
electronicMedicalRecords/Contact	X	X		X	X				X
[samples]electronicMedicalRecords/Contact	X	X		X	X				X
electronicMedicalRecords/FamilyMemberHistory	X	X		X	X
clinicalCore/FamilyMemberHistory	X	X		X	X
loanApplicationContact	X	X	X					X
retailBankingCoreDataModel/GlobalOptionSets	X	X	X					X

[dingbx]

Hi Lee,

The schema can't be updated by us, it is defined by the Dataverse solution provider. We have created a task to track this issue and will reach out to Dataverse to update the schema. We can't merge the PR directly from GitHub, but please feel free to send the PR and we will use it as a reference.

Thanks,
Yijing

[lee0c]

Closing as this needs to be handled at other levels.