Release 5 Ballot

This page is part of the FHIR Specification (v5.0.0-ballot: R5 Ballot - see ballot notes). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B

Patient Administration icon Work GroupMaturity Level: N/AStandards Status: Informative
Defines common extensions used with or related to the Patient resource
Extensions:
patient-mothersMaidenNamemothersMaidenName :

Mother's maiden (unmarried) name, commonly collected to help verify patient identity.

no-fixed-addressNoFixedAddress :

This extension applies to the Address data type and is used to indicate that a location address is not a fixed address for an individual.

patient-birthPlacebirthPlace :

The registered place of birth of the patient. A sytem may use the address.text if they don't store the birthPlace address in discrete elements.

patient-birthTimebirthTime :

The time of day that the Patient was born. This includes the date to ensure that the timezone information can be communicated effectively.

patient-multipleBirthTotalmultipleBirthTotal :

Where a patient is a part of a multiple birth, this is the total number of births that occurred in this pregnancy.

This value is the 4 in '3 of 4', and the 3 would be the Patient.multipleBirth value.

patient-nationalitynationality :

The nationality of the patient.

patient-citizenshipcitizenship :

The patient's legal status as citizen of a country.

patient-cadavericDonorcadavericDonor :

Flag indicating whether the patient authorized the donation of body parts after death.

patient-congregationcongregation :

A group or place of religious practice that may provide services to the patient.

patient-adoptionInfoadoptionInfo :

Code indication the adoption status of the patient.

patient-disabilitydisability :

Value(s) identifying physical or mental condition(s) that limits a person's movements, senses, or activities.

patient-importanceimportance :

The importance of the patient (e.g. VIP).

patient-interpreterRequiredinterpreterRequired :

This Patient requires an interpreter to communicate healthcare information to the practitioner.

patient-religionreligion :

The patient's professed religious affiliations.

patient-relatedPersonrelatedPerson :

In some cases a Patient.contact will also be populated as a RelatedPerson resource. This linkage permits the linkage between the 2 resources to be able to accurately indicate a representation of the same individual, and updating details between could be appropriate.

individual-genderIdentitygenderIdentity :

An individual's personal sense of being a man, woman, boy, girl, nonbinary, or something else. This represents an individual’s identity, ascertained by asking them what that identity is.

patient-sexForClinicalUsesexForClinicalUse :

Sex for Clinical Use (SFCU) Overview

Sex for Clinical Use is a categorization of sex derived from observable information such as an organ inventory, recent hormone lab tests, genetic testing, menstrual status, obstetric history, etc. This property is intended for use in clinical decision making and indicates that treatment or diagnostic tests should consider best practices associated with the relevant reference population.

While clinical decision-making processes could account for the specific physiological or anatomical attributes of the patient, there are several practical considerations, such as patient privacy and limited capabilities of existing systems which create the need for a categorization that is easy to exchange. The Sex for Clinical Use categorization is intended to bridge the gap between the hypothetical ideal and the practical needs of operational systems.

Sex for Clinical Use (SFCU) Contexts

Sex for Clinical Use is a contextual concept. For example, a patient may generally be categorized as male, but for a specific lab test, the resulting lab should use the reference ranges associated with a female reference population. In this case, systems may provide a patient-context sexForClinicalUse that acts as a 'default' for most care and annotate the lab order with a context-specific sexForClinicalUse. Systems may determine what enclosing contexts are useful, but Patient, Encounter and EpisodeOfCare are three enclosing contexts that may often apply.

The sexForClinicalUse extension can be used to communicate a clinical sex category on the on relevant clinical resources (e.g., DiagnosticReport, ServiceRequest) or enclosing contexts (e.g., Patient, Encounter, EpisodeOfCare).

Sex for Clinical Use (SFCU) Categorization

For ease of interoperability, a patient’s sex for clinical use is constrained to four possible categories. Any patient for which special considerations apply should be categorized as 'Specified'. The 'Specified' category is often represented as 'Other' in existing systems.

Female - Available data indicates that diagnostics, analytics, and treatments should consider best practices associated with female reference populations.

Male - Available data indicates that diagnostics, analytics, and treatments should consider best practices associated with male reference populations.

Specified - Available data indicates that diagnostics, analytics, and treatment best practices may be undefined or not aligned with existing sex-derived reference populations. Individuals or systems providing care should either use default behavior that is safe for both male and female populations, individually review treatment options with the patient, or carefully inspect relevant observations before proceeding with treatment.

Unknown - The sex for clinical use cannot be determined because there are no relevant evidence or documentation, or the evidence or documentation are not sufficient to determine a value. Sex for Clinical Use (SFCU) History and Practices

Prior to the definition of Sex for Clinical Use as a concept, systems may have used administrative gender as an approximation of patient-level sex for clinical use. This practice required pre-coordination among exchange parters to explicitly overload the administrative sex concept for use as a clinical sex concept. In cases where there was no pre-coordination, some systems may have incorrectly inferred information about a patient's clinical sex from administrative gender.

In the context of ordering workflows, systems may use Ask at Order Entry (AOE) questions to collect concepts similar to sex for clinical use.

individual-recordedSexOrGenderrecordedSexOrGender :

The recorded sex and gender is to be used to differentiate existing sex or gender data. This element is used for existing 'sex' or 'gender' elements in a document or record when the intent and meaning is unclear. For example, the individual's birth certificate information, passport information, and national identity document information may all be present. This is necessary because an individual's documents may be updated at different rates or for different reasons. Sex assigned at birth (SAAB), while very common and considered essential in some jurisdictions, is considered a recorded sex and gender entry.

individual-pronounspronouns :

The pronouns to use when referring to an individual in verbal or written communication.

patient-preferenceTypepreferenceType :

Indicates what mode of communication the patient prefers to use for the indicated language.

patient-animalanimal :

This patient is known to be an animal.

patient-proficiencyproficiency :

Proficiency level of the communication.

Search parameters defined by this package. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionPathsSource
agenumberSearches for patients based on age as calculated based on current date and date of birth. Deceased patients are excluded from the search.Patient.birthDateXML / JSON
birthOrderBooleantokenSearch based on whether a patient was part of a multiple birth or not.Patient.multipleBirthBoolean | Patient.multipleBirthIntegerXML / JSON
mothersMaidenNamestringSearch based on patient's mother's maiden namePatient.extension('http://hl7.org/fhir/StructureDefinition/patient-mothersMaidenName').valueXML / JSON