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 22 Next »

  • Elizabeth Storrs after Vet cycle is done, migrate CAS/Liaison gender field to standard Gender Identity field; migrate CAS/Liaison sex field to gender marker
  • create new marker and identity fields in TUH
  • discuss next move with Dmitri

random note: in Slate, the delivered sex field is going to have a great deal of data in it, since we have been using it from the beginning . Merging newer records into older records may generate phantom values in this field, and we need to be very careful not to be using those values when they have not been maintained.

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.

 AMCAS/TUSM

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.”

In AMCAS, the reference table for this past 2024 season has the following values:

image-20240829-161403.png

Code: SELECT * FROM AmcasDES.amcas.REFERENCE_Gender WHERE APPL_YEAR = 2024 ORDER BY DISPLAY_SEQ

image-20240627-204213.png

The 2024 applicant data also has a "sex" column:

Code: SELECT sex,COUNT(*) AS cnt FROM [AmcasDES].[amcas].[AMCAS_Applicant] WHERE app_year = 2024 GROUP BY sex ORDER BY cnt desc

image-20240627-204253.png

I also see 2024 applicant data on gender identity. I'm currently ignoring this data in terms of SIS and Stuart:

Code: SELECT  gender_identity_code,gender_identity,COUNT(*) AS cnt FROM [AmcasDES].[amcas].[ApplicantPersonalInfo] WHERE app_year=2024 GROUP BY gender_identity_code,gender_identity ORDER BY COUNT(*) desc

gender_identity_code

gender_identity

cnt

F

Woman

7,984

M

Man

5,505

NULL

NULL

630

NB

Non-binary

54

GQ

Genderqueer/Gender non-conforming

23

F;GQ

Woman; Genderqueer/Gender non-conforming

19

GQ;NB

Genderqueer/Gender non-conforming; Non-binary

18

M;NB

Man; Non-binary

14

F;NB

Woman; Non-binary

12

M;GQ

Man; Genderqueer/Gender non-conforming

7

TF

Trans woman

7

A

Agender

5

TM

Trans man

5

M;TM

Man; Trans man

3

M;GQ;NB

Man; Genderqueer/Gender non-conforming; Non-binary

2

F;A

Woman; Agender

2

A;GQ;NB

Agender; Genderqueer/Gender non-conforming; Non-binary

2

A;GQ

Agender; Genderqueer/Gender non-conforming

1

A;NB

Agender; Non-binary

1

NB;O

Non-binary; Another Gender Identity - genderfluid

1

O

Another Gender Identity - Butch

1

NB;O

Non-binary; Another Gender Identity - Genderqueer/gender diverse

1

O

Another Gender Identity - Khwaja-Sira (Pak-Indigenous gender-spirituality)

1

TM;GQ;NB

Trans man; Genderqueer/Gender non-conforming; Non-binary

1

GQ;NB;O

Genderqueer/Gender non-conforming; Non-binary; Another Gender Identity - Transgender

1

TF;NB

Trans woman; Non-binary

1

M;A

Man; Agender

1

F;GQ;NB

Woman; Genderqueer/Gender non-conforming; Non-binary

1

TM;GQ

Trans man; Genderqueer/Gender non-conforming

1

NB;O

Non-binary; Another Gender Identity - I identify under the transgender umbrella

1

NB;O

Non-binary; Another Gender Identity - Intersex

1

F;TF;NB

Woman; Trans woman; Non-binary

1

For interfacing with SIS, the SQL view uses these values:   O, U, M, F, U

 CASE

           WHEN vw.GENDER = 'Another Gender' THEN

               'O'

           WHEN vw.GENDER = 'Decline to Answer' THEN

               'U'

           WHEN vw.GENDER = 'Man' THEN

               'M'

           WHEN vw.GENDER = 'Woman' THEN

               'F'

           ELSE

               'U'

       END AS SEX

And lastly, Stuart supports these values currently, though Bruce suspects this will change very soon:

Code: SELECT DISTINCT sex, gender.Gender FROM student st INNER JOIN register re ON re.StudentKey = st.StudentKey LEFT JOIN gender ON gender.GenderCode = st.Sex WHERE re.RegType = 'DegreeProgram' AND sex IS NOT null

sex

Description

F

Female

A

Another Gender Identity

M

Male

D

Declined to provide

 Dental

Dental is unusual in that there is no automation from the 3 CAS systems (ADEA, AADSAS, PASS) and the local Qualtrics application; Mario does a data upload to SIS.

ADEA/AADSAS

image-20240829-162306.png

Summary sheet of all incoming admissions data

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

Conversation with Hope Freeman 7/10/2024

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

Is not sent to Powerfaids or for Students to or from HR.

  • No labels