Problem/Motivation

Some site builder will need a sex field.

Steps to reproduce

Proposed resolution

Include a sex field, but do not include it on any contact bundles.

➡️ This follows ISO/IEC 5218, an international standard used in medical and census data

Code Label Notes
0 Unknown Data unavailable
1 Male Assigned male at birth
2 Female Assigned female at birth
9 Not applicable For non-human or administrative records

No significance is to be placed upon the fact that “Male” is coded “1” and “Female” is coded “2”. This
document was developed based upon predominant practices of the countries involved and does not convey any meaning of importance, ranking or any other basis that can imply discrimination.

Used in healthcare, research, and government contexts that recognize exceptions and unknown data.
Standard developed by Health Level Seven International (HL7)

Code Label Notes
M Male Assigned male at birth
F Female Assigned female at birth
I Intersex Anatomical/physiological variance
U Unknown Data unavailable
N Not applicable For non-human or administrative records

We could also include:
P
Prefer not to say

The field not being required can serve a similar intend.

Remaining tasks

User interface changes

API changes

Data model changes

Only add the field storage

CommentFileSizeAuthor
#3 ISO-IEC-5218-2022-sexes.pdf1006.87 KBbluegeek9

Issue fork crm-3555594

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

bluegeek9 created an issue. See original summary.

bluegeek9’s picture

Issue summary: View changes
bluegeek9’s picture

Issue summary: View changes
StatusFileSize
new1006.87 KB
bluegeek9’s picture

Issue summary: View changes
bluegeek9’s picture

Issue summary: View changes

bluegeek9’s picture

Status: Active » Needs review

The admin login to the tugboat instance is admin:admin

bluegeek9 changed the visibility of the branch 1.0.x to hidden.

jdleonard’s picture

Version: 1.0.0-alpha6 » 1.0.x-dev

Fixing version.

svendecabooter made their first commit to this issue’s fork.

svendecabooter’s picture

Provided some feedback.
If it is not deemed appropriate, then I think this is ready to go. Is there a reason the MR is still in draft state?

jdleonard’s picture

Aside: I'm not sure the base module should be providing and maintaining fields like this. This feels like something better suited to a separate module or recipe.

bluegeek9’s picture

Category: Feature request » Plan
Priority: Normal » Minor
Status: Needs review » Active

Making a plan to indicate that this is meant for discussion before implementation. The ultimate solution might not seide in the crm namespace/project.

bluegeek9 changed the visibility of the branch 3555594-demographic-sex to hidden.

bluegeek9’s picture

Category: Plan » Task
Status: Active » Needs review
bluegeek9’s picture

Status: Needs review » Fixed
//www.flaticon.com/free-icons/thank-you Thank you for your contribution! Your continued support makes this project sustainable.
There are multiple ways to show appreciation for the work contributed to this project including:
  • Triage issues and adding more context to existing issues.
  • Flagging CRM as a favorite on the project page to help others discover it and show your support.
  • Review the Developer Docs for accuracy and clarity.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.