Sex field: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
No edit summary
 
(8 intermediate revisions by 2 users not shown)
Line 12: Line 12:
}}
}}


Also see [[Guidelines for coding sex and gender]].
{{DiscussTask|
* 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. [[User:Ttenbergen|Ttenbergen]] 00:16, 12 November 2025 (CST)
}}
== Sex changes over time ==
== 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.
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.


EPR uses 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.'''
As discussed at [[Task Team Meeting - Rolling Agenda and Minutes 2019#ICU Database Task Group Meeting – June 26, 2019 |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.'''  


{{DiscussTask | If EPR stores current, and a lot of our data comes only from EPR or chart, then for any patients where we don't have a previous, recognizable encounter, we may not be storing their sex assigned at birth even now. Is this true? If so, do we want to change how we treat this field as a result? }}
{{Data Integrity Check List}}


== Related Articles ==
== Related Articles ==
{{Related Articles}}
{{Related Articles}}


[[Category: Data Collection Guide]]
[[Category:Data Collection Guide]]
[[Category: Registry Data]]
[[Category:Registry Data]]
[[Category: ALERT Scale Elements]]
[[Category:ALERT Scale Elements]]
[[Category: Demographics]]
[[Category:Demographics]]

Latest revision as of 00:16, 12 November 2025

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)

 AppStatus
PL SamePhin Diff DOB SexCentralized data front end.accdbimplemented

Related Articles

Related articles: