Sex field

Data Element (edit)
Field Name:	R_Sex
CCMDB Label:	Sex
CCMDB tab:	Dispo
Table:	L_Log table
Data type:	string
Length:	7
Program:	Med and CC
Created/Raw:	Raw
Start Date:	1988-07-11
End Date:	2300-01-01
Sort Index:	17
Data Dependencies(Reports/Indicators/Data Elements):	No results

Biological sex of the patient at birth; options are "male" and "female".

• SMW

Legacy implementation right in the table

• Cargo

• Categories

• Forms

Also see Guidelines for coding sex and gender.

I just came across an incomplete record (from S9 laptop) that has a sex entry "Undiff". Our dropdown doesn't contain this so this likely came from Cognos. If this is now being coded in EPR, and considering that this would affect the "biological sex" we use in defining this, should we introduce this as an option? If we do not want to introduce this as an option, do our cross checks catch this? They might not, since this could not have been entered manually. Ttenbergen 00:16, 12 November 2025 (CST)

• SMW

• Cargo

• Categories

Sex changes over time

Also see Biographic changes over time

For those patients who are transgender or transsexual, document what their sex was at birth. This may mean that a record's FirstName field becomes inconsistent with their Sex field. In those cases, the contents of the Alias_ID_collection might shed lights on the reason.

As discussed at Task, EPR used the currently used gender, as far as we could tell. We didn’t review what the policies are about this. Our records may therefore be inconsistent with EPR.

Data Integrity Checks (automatic list)

	App	Status
PL SamePhin Diff DOB Sex	Centralized data front end.accdb	implemented