Sex field: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m cat |
Ttenbergen (talk | contribs) No edit summary |
||
| (13 intermediate revisions by 3 users not shown) | |||
| Line 4: | Line 4: | ||
| CCMDB_tab = Dispo | | CCMDB_tab = Dispo | ||
| element_description = Biological sex of the patient at birth; options are "male" and "female". | | element_description = Biological sex of the patient at birth; options are "male" and "female". | ||
| in_table = L_Log | | in_table = L_Log table | ||
| data_type = string | | data_type = string | ||
| datafield_length = 7 | | datafield_length = 7 | ||
| Line 12: | Line 12: | ||
}} | }} | ||
Also see [[Guidelines for coding sex and gender]]. | |||
[[Category: Data Collection Guide]] | {{DiscussTask| | ||
[[Category: Registry Data]] | * 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) | ||
[[Category: | }} | ||
[[Category: Demographics]] | == 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 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.''' | |||
{{Data Integrity Check List}} | |||
== Related Articles == | |||
{{Related Articles}} | |||
[[Category:Data Collection Guide]] | |||
[[Category:Registry Data]] | |||
[[Category:ALERT Scale Elements]] | |||
[[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".
Also see Guidelines for coding sex and gender.
|
|
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 |
Related Articles
| Related articles: |
|