AU Patient Summary Implementation Guide
0.5.0-preview - Preview

AU Patient Summary Implementation Guide - Downloaded Version 0.5.0-preview See the Directory of published versions

## 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 Patient Summary (AU PS).

AU PS is based on AU Core profiles, inheriting Must Support flags on some concepts, and inherits sex and gender related elements localised in AU Base. Work in AU Base 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 PS through inheritance from AU Core and compliant to IPS.

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 relevant and not yet localised for use in an Australian context.

Not Applicable: This sex or gender related concept is not applicable for use with this resource type.

Sex and Gender Concept | Administrative Gender | Name to Use | Pronouns | Gender Identity | Recorded Sex or Gender | Sex Assigned at Birth | Sex Parameter for Clinical Use (SPCU)
--- | --- | --- | --- | --- | --- | --- | ---
AU PS Patient |  |  |  |  |  |  |
AU PS Practitioner |  |  |  |  |  |  |
AU PS RelatedPerson |  |  |  |  |  |  |
AU PS MedicationRequest |  |  |  |  |  |  |
AU PS Procedure |  |  |  |  |  |  |

### Administrative Gender (Patient.gender)

AU PS Patient supports the exchange of Administrative Gender, i.e. the basic `Patient.gender` property, as a Must Support element in AU PS Patient. As per AU Base, the `Patient.gender` value SHALL be regarded as a Recorded Sex or Gender. AU PS 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 (NtU)

AU PS supports the exchange of the Name to Use data element (as defined in the HL7 Gender Harmony IG), `name.use` is a Must Support element in AU PS Patient and AU PS RelatedPerson. It is important to note that, `name.period` is not a Must Support element. AU PS adopts without change, the implementation guidance defined in the Name to Use (NtU) section of the AU Base Sex and Gender page.

### Pronouns​

AU PS supports the exchange of the Pronouns data element (as defined in the HL7 Gender Harmony IG), the Individual Pronouns extension is a Must Support element in AU PS Patient, with the value element of the extension constrained to be Australian Pronouns (extensible). AU PS adopts without change, the implementation guidance defined in the Pronouns section of the AU Base Sex and Gender page.

### Gender Identity (GI)

AU PS supports the exchange of the Gender Identity data element (as defined in the HL7 Gender Harmony IG), the Individual Gender Identity extension is a Must Support element in AU PS Patient, with the value element of the extension constrained to be Gender Identity Response (extensible). AU PS adopts without change, the implementation guidance defined in the Gender Identity (GI) section of the AU Base Sex and Gender page.

### Recorded Sex or Gender

In AU PS, Recorded Sex or Gender is not Must Support. See the implementation guidance defined in the Recorded Sex or Gender section of the AU Base Sex and Gender page for more information.

### Sex Assigned at Birth

In AU PS, SPCU is not Must Support. See the implementation guidance defined in the Sex Assigned at Birth section of the AU Core Sex and Gender page for more information.

### Sex Parameter for Clinical Use (SPCU)

In AU PS, SPCU is not Must Support. See the implementation guidance defined in the Sex Parameter for Clinical Use (SPCU) section of the AU Base Sex and Gender page for more information.