Versions Compared

Version Old Version 22 New Version 23
Changes made by

Elizabeth Storrs

Elizabeth Storrs

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

...

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

To get data into that field,

at some point

Mapping from Slate Identity/Marker to Slate . If gender does not match withinSex for consumption by SIS:

Coalesce: Identity first, then Marker.

Male/M → Male

Female/F → Female

Transmasculine/Transman → Transgender

Transfeminine/Transwoman → Transgender

Prefer to Specify → Other

Non-binary → Nonbinary

Decline to State → blank

X → Indeterminate/Intersex/Unspecified

text fields (”other” description) may be brought into Slate, but cannot go to SIS

...

Automated update of “sex” field within Slate

TUP Transition Gender Fields

Create Scheduled Query SFTP Process

Using the work Helen did in TUSMGP as a model, there is now an automated query in Vet and in TUH that will update the delivered ‘sex’ value with a concatenated Identity/Marker value; the Assign Sex field for SIS interface queries are set to run between 2-4 pm to get the updates before data is pulled for SIS. These run to the Trigger: Person - Sex source format.

Note: when copying over the query, the

When copying over the query, the ‘extended’ export value Helen had set in the concatenated sex export gets reset to “default”. The mapping existed for M and F, but NB value was not mapped anywhere. 12/2 Updated both the mapping, so NB flows correctly, but also updated the export values.

TUH Assign Sex field for SIS interface query was started on 11/27/2024.

  • 12/2 reviewed imports and updated anyone with an NB value by hand on their application record

In the applications we control, should we be asking for “other”, even if we cannot send that to SIS? Is it just performative? Elizabeth Storrs ask Hope!

SIS

Everything ultimately has to flow into SIS.

...