Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

The required ‘legal sex’ v. optional ‘preferred gender’ in the CAS systems is a decent entry point to thinking about sex/gender as a core data point within the Tufts data ecosystem.

Incoming Data

There are a variety of ways that this data is offered.

The CAS systems are detailed here; in

AMCAS https://students-residents.aamc.org/applying-medical-school-amcas/publication-chapters/gender-identity-and-pronouns

“You should answer the gender question based on the gender with which you identify, which may or may not be the sex you were assigned at birth. Gender Identity is a separate, optional question intended to draw out additional layers of student body diversity, including diverse perspectives from applicants who have experienced major life events or transitions related to their gender identity.”

Slate to SIS

This is mapped from the delivered, person-scoped Sex field in Slate.

If gender does not match within

SIS

Everything ultimately has to flow into SIS.

image-20240617-180719.pngimage-20240617-180635.png

Interestingly enough, there are other (delivered) options for tracking this data in SIS that have been added since 2017, when we added new sex/gender options.

image-20240626-144459.png

From SIS

Of course, any changes in SIS affect downstream things!

Medicat

Jonathan Pritchard 6/24/2024:

Sex in Medicat, has 4 options. In reviewing the SIS file, only M/F/U are populated (outliers mapped to U), but a [staff] user in Medicat can change the sex if needed.

  • Female

  • Male

  • Transgender

  • Unknown

There are also user-defined options to capture pronouns and gender identity--these are updated manually.

image-20240626-142708.png

  • No labels