Gender Model Standards – Beyond Male and Female

data modelingdatabase-designdomain-model

I am modeling a database that should be used as generic non-functional requisite for all services of the startup company, like persons, users, services and commercial data like coupons, signature packages, etc.

I am thinking about the gender model. In these modern days and with different laws across countries about subjective identity, should I take that into consideration and model my Person entity with more than just the male and female options?

Options are: undefined, not-answered, other, transgender… or any other industry standard that I am unaware of…

Or does this offend LGBT people by saying that they are not truly male or female?

Best Answer

Sometimes the term gender may be used when sex is meant. Sex is defined by a person's biological traits whereas gender is determined by identity.

The standard for sex is codified by the ISO/IEC 5218 standard [download].

There are four available values

0 = not known,
1 = male,
2 = female,
9 = not applicable

Similar values can be given for gender

male
female
non-binary
prefer not to say
Related Topic