Name Flags Card. Type Description & Constraints Extension 0..* Extension A recorded sex or gender property for the individual extension:value 1..1 Extension The recorded sex or gender property for the individual extension 0..0 url 1..1 uri "value" value[x] 1..1 CodeableConcept Value of extension Binding: AdministrativeGender (example) extension:type 0..1 Extension Type of recorded sex or gender. extension 0..0 url 1..1 uri "type" value[x] 1..1 CodeableConcept Value of extension Binding: Recorded Sex Or Gender Type (example) extension:effectivePeriod 0..1 Extension When the recorded sex or gender value applies extension 0..0 url 1..1 uri "effectivePeriod" value[x] 0..1 Period Value of extension extension:acquisitionDate 0..1 Extension When the sex or gender value was recorded. extension 0..0 url 1..1 uri "acquisitionDate" value[x] 1..1 dateTime Value of extension extension:sourceDocument 0..1 Extension The document the sex or gender property was acquired from. extension 0..0 url 1..1 uri "sourceDocument" Slices for value[x] 1..1 CodeableConcept, Reference() Value of extension Slice: Unordered, Closed by type:$this value[x]:valueCodeableConcept 0..1 CodeableConcept Value of extension value[x]:valueReference 0..1 Reference(DocumentReference) Value of extension extension:sourceField 0..1 Extension The name of the field within the source document where this sex or gender property is initially recorded. extension 0..0 url 1..1 uri "sourceField" value[x] 1..1 string Value of extension extension:jurisdiction 0..1 Extension Who issued the document where the sex or gender was aquired extension 0..0 url 1..1 uri "jurisdiction" value[x] 1..1 CodeableConcept Value of extension Binding: Jurisdiction ValueSet (extensible) extension:comment 0..1 Extension Context or source information about the recorded sex or gender extension 0..0 url 1..1 uri "comment" value[x] 1..1 string Value of extension url 1..1 uri "http://hl7.org/fhir/StructureDefinition/individual-recordedSexOrGender" value[x] 0..0 Documentation for this format
Recorded sex or gender (RSG) information includes the various sex and gender concepts that are often used in existing systems but are known NOT to represent a gender identity, sex parameter for clinical use, or attributes related to sexuality, such as sexual orientation, sexual activity, or sexual attraction. Examples of recorded sex or gender concepts include administrative gender, administrative sex, and sex assigned at birth. When exchanging this concept, refer to the guidance in the [Gender Harmony Implementation Guide](http://hl7.org/xprod/ig/uv/gender-harmony/). This extension is published in this guide to pre-adopt an extension published in the R5 [FHIR Extensions Pack](http://hl7.org/fhir/extensions/StructureDefinition-individual-recordedSexOrGender.html). The only material difference is the data type for extension part sourceDocument (R5 CodeableReference to a choice between R4 CodeableConcept or Reference).
HL7 Australia© 2018+; Licensed Under Creative Commons No Rights Reserved.
A recorded sex or gender property for the individual
A sex or gender property for the individual from a document or other record
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
The recorded sex or gender property for the individual
Source of the definition for the extension code - a logical name or a URL.
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).
The type or category of sex or gender that is recorded.
Because the recorded sex or gender concept exists primarily as means to exchange sex and gender data concepts that are known NOT to represent a gender identity, sex parameter for clinical use, or attributes related to sexuality, the type is used to identify what type of concept the recorded sex or gender concept is.
When the recorded sex or gender value applies
The time period during which the recorded sex or gender value applies to the individual
When the sex or gender value was recorded.
The date/time when the sex or gender value was first recorded in the system.
The document the sex or gender property was acquired from.
The reference to the source document or the code representing the type of document where this sex or gender property is initially recorded.
For example, if a driver's license is scanned, this property may reference that scanned document.
The name of the field within the source document where this sex or gender property is initially recorded.
For example, if a sex value is acquired from a driver's license, and the name of the field on that driver's license is 'SEX', then a code describing that field can be provided. If the semantics of the field are known, they may be described in the comment. For example, if the 'SEX' field on a license in a particular state or province is populated based on an individual's indication of what gender they consider themselves to be, but the field label is 'SEX' for historical reasons, a comment describing that the semantics of the field align with gender identity, even though the field name is 'SEX' can be provided.
Who issued the document where the sex or gender was aquired
The jurisdiction or organization that issued the document from which the sex or gender was aquired
For example, a individual's driver's license or passport would be issued by a specific state or country.
Context or source information about the recorded sex or gender
Further explanation about the context or source of the recorded sex or gender value