AU eRequesting Implementation Guide
0.3.0-preview - Preview

Publication Build: This will be filled in by the publication tooling

## Sex and Gender

Page standards status: Informative

This page addresses how sex and gender related concepts can be structured in FHIR and conformant to AU eRequesting.

AU eRequesting references AU Base and AU Core profiles which represent sex and gender concepts. AU Cores places Must Support on some concepts and inherits sex and gender related elements localised in AU Base, which has considered the logical data element models provided by HL7 International’s Cross Paradigm Implementation Guide: Gender Harmony - Sex and Gender Representation, Edition 1 specification.

The table below provides an overview of the sex and gender concepts that are included in AU eRequesting through reference to AU Core and AU Base.

Legend:

Supported: The sex or gender related concept is marked as Must Support.

Localised: The sex or gender related concept is localised for use in an Australian context but is not marked as Must Support.

Not localised: The sex or gender related concept is not localised for use in an Australian context.

Sex and Gender Concept | AU Core Patient | AU Core Practitioner | AU Base Related Person
--- | --- | --- | ---
Administrative Gender (Patient.gender) |  |  |
Name to Use |  |  |
Pronouns |  |  |
Gender Identity |  |  |
Recorded Sex or Gender |  |  |
Sex Assigned at Birth |  |  |

### Administrative Gender (Patient.gender)

By reference to AU Core Patient, AU eRequesting supports the exchange of Administrative Gender, i.e. the basic `Patient.gender` property, as a Must Support element in AU Core Patient. As per AU Base, the `Patient.gender` value SHALL be regarded as a Recorded Sex or Gender. AU Core adopts without change, the implementation guidance defined in the Administrative Gender (Patient.gender) section of the AU Base Sex and Gender page.

### Name to Use

By reference to AU Core Patient, AU eRequesting supports the exchange of the Name to Use data element (as defined in the HL7 Cross Paradigm Implementation Guide: Gender Harmony - Sex and Gender Representation, Edition 1), and `name.use` is a Must Support element in AU Core Patient. It is important to note that, `name.period` is not a Must Support element. AU Core adopts without change, the implementation guidance defined in the Name to Use section of the AU Base Sex and Gender page.

### Pronouns​

By reference to AU Core Patient, AU eRequesting supports the exchange of the Pronouns data element (as defined in the HL7 Cross Paradigm Implementation Guide: Gender Harmony - Sex and Gender Representation, Edition 1). The Individual Pronouns extension is a Must Support element in AU Core Patient, with the value element of the extension constrained to be Australian Pronouns (extensible). AU Core adopts without change, the implementation guidance defined in the Pronouns section of the AU Base Sex and Gender page.

### Gender Identity

By reference to AU Core Patient, AU eRequesting supports the exchange of the Gender Identity data element (as defined in the HL7 Cross Paradigm Implementation Guide: Gender Harmony - Sex and Gender Representation, Edition 1). The Individual Gender Identity extension is a Must Support element in AU Core Patient, with the value element of the extension constrained to be Gender Identity Response (extensible). AU Core adopts without change, the implementation guidance defined in the Gender Identity section of the AU Base Sex and Gender page.

### Sex Assigned at Birth

In AU Core, Sex Assigned at Birth is profiled as AU Core Sex Assigned At Birth. While elements within AU Core Sex Assigned at Birth are Must Support, usage of the profile is not Must Support in AU Core Patient which is referenced by AU eRequesting. That profile provides an implementation of the guidance in the Sex Assigned at Birth section of the AU Base Sex and Gender page.