Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
US Core (FHIR)
-
current
-
Cross-Group Projects
-
US Core Sex Extension
-
-
Brett Marquard/Eric Haas: 17-0-0
-
Enhancement
-
Compatible, substantive
Description
The Sex Extension profile is designed to implement the [Sexhttps://www.healthit.gov/isa/taxonomy/term/731/uscdi-v3] data element in USCDI v3, where it can be any instance of sex info: birth sex, legal sex, you name it.
However, the value set that it's bound to is super tightly constrained. The sex has to be one of four values (male, female, unknown, or "asked but declined") and nullFlavors aren't allowed--if you can't map a sex to one of those four, you can't send it at all!
But if we truly want this template to capture the full spectrum of USCDI v3 Sex, then we need to broaden it. In particular, it doesn't work with legal sex right now--if the sex on your drivers license is "X" or "nonbinary" or anything to that effect, there's no way to send it!
I think we need to expand the value set, but we should probably discuss with Gender Harmony and/or CGP.
Attachments
Issue Links
- relates to
-
FHIR-44764 Change binding on Sex Extension's value set from required to extensible?
- Applied
-
FHIR-45177 Add Guidance on new SNOMED Concept added to support 'X'
- Applied
-
FHIR-44785 Remove binding to SCT or relax to "example"
- Duplicate
-
CDA-21060 Sex Observation's value set is too restrictive
- Applied
-
CDA-21065 Remove binding to SCT or relax to "may"
- Applied