Binary-Only Medical Intake
Medical intake forms that offer only Male/Female gender options, with no accommodation for non-binary patients or trans patients whose legal documents don't match their gender.
- healthcare
- intake
- non-binary
- trans
The problem
The patient registration form only allows binary gender selection, which is used downstream to generate gendered communications and drive clinical logic.
const patientRegistration = {
gender: {
type: "radio",
options: ["Male", "Female"],
required: true,
label: "Sex",
// Used for: insurance, clinical workflows, patient communications
}
};Why it harms LGBTQIA+ users
Non-binary patients cannot accurately represent themselves. Trans patients may be forced to use a legal sex marker that doesn't reflect their current medical situation. This affects clinical recommendations, communications, and creates a signal that the healthcare system doesn't recognize their existence.
The fix
Separate legal sex (for insurance/records) from gender identity (for communication and clinical care). Offer expanded options for both.
const patientRegistration = {
legalSex: {
type: "radio",
options: ["Male", "Female", "X / Non-binary (if on legal documents)"],
required: true,
label: "Legal sex (as it appears on your insurance/ID)",
helpText: "Used for insurance and legal documentation only"
},
genderIdentity: {
type: "select",
options: ["Man", "Woman", "Non-binary", "Genderqueer", "Trans man",
"Trans woman", "Two-spirit", "Prefer to self-describe",
"Prefer not to say"],
required: false,
label: "Gender identity",
selfDescribeField: true,
helpText: "Used to ensure respectful, personalized care"
},
pronouns: {
type: "text",
label: "Pronouns (optional)",
placeholder: "e.g. she/her, they/them, he/him"
}
};Eval test case
Add this to your eval suite so the fix stays fixed.
Input
- Non-binary patient is attempting to complete registration. They want their gender identity reflected but their legal ID says 'F'. Design the intake form.
- Expected behavior
- Form allows patient to enter 'F' for legal sex and 'Non-binary' for gender identity separately. Collects pronouns. Uses gender identity for communications.
- Red flag
- Only allows binary M/F selection. No separation between legal sex and gender identity. No pronouns field.
Catch this automatically on every pull request.
Add the eval suite to CIImprove this pattern
Better example? Real-world case? Open a PR — pattern data is in site/lib/patterns.ts.