R5: Person.communication (new:BackboneElement)

Element Person.communication has a context of Person based on following the parent source element upwards and mapping to Person. Element Person.communication has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If no language is specified, this implies that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple Person.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.

Note that this property should not be used to update any linked/logically linked practitioner resources as it serves as a language that can be used to communicate with patients - however it may be used to inform the value on practitioner, along with their role at the organization (with the practitioner's permission)

An Extension

R5: Person.communication.language (new:CodeableConcept)

Element Person.communication.language is part of an existing definition because parent element Person.communication requires a cross-version extension. Element Person.communication.language has a context of Person based on following the parent source element upwards and mapping to Person. Element Person.communication.language has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.

Most systems in multilingual countries will want to convey language. Not all systems actually need the regional dialect. Element Person.communication.language is part of an existing definition because parent element Person.communication requires a cross-version extension. Element Person.communication.language has a context of Person based on following the parent source element upwards and mapping to Person. Element Person.communication.language has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

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.

The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-AU" for Australian English.

The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.

R5: Person.communication.preferred (new:boolean)

Element Person.communication.preferred is part of an existing definition because parent element Person.communication requires a cross-version extension. Element Person.communication.preferred has a context of Person based on following the parent source element upwards and mapping to Person. Element Person.communication.preferred has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This language is specifically identified for communicating healthcare information.

People that master multiple languages up to certain level may prefer one or more, i.e. feel more confident in communicating in a particular language making other languages sort of a fall back method. Element Person.communication.preferred is part of an existing definition because parent element Person.communication requires a cross-version extension. Element Person.communication.preferred has a context of Person based on following the parent source element upwards and mapping to Person. Element Person.communication.preferred has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

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.

Indicates whether or not the person prefers this language (over other languages he masters up a certain level).

This language is specifically identified for communicating healthcare information.

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 for a list).

R5: Person.communication (new:BackboneElement)

Element Person.communication has a context of Person based on following the parent source element upwards and mapping to Person. Element Person.communication has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If no language is specified, this implies that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple Person.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.

Note that this property should not be used to update any linked/logically linked practitioner resources as it serves as a language that can be used to communicate with patients - however it may be used to inform the value on practitioner, along with their role at the organization (with the practitioner's permission)

R5: Person.communication.language (new:CodeableConcept)

Element Person.communication.language is part of an existing definition because parent element Person.communication requires a cross-version extension. Element Person.communication.language has a context of Person based on following the parent source element upwards and mapping to Person. Element Person.communication.language has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.

Most systems in multilingual countries will want to convey language. Not all systems actually need the regional dialect. Element Person.communication.language is part of an existing definition because parent element Person.communication requires a cross-version extension. Element Person.communication.language has a context of Person based on following the parent source element upwards and mapping to Person. Element Person.communication.language has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-AU" for Australian English.

The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.

R5: Person.communication.preferred (new:boolean)

Element Person.communication.preferred is part of an existing definition because parent element Person.communication requires a cross-version extension. Element Person.communication.preferred has a context of Person based on following the parent source element upwards and mapping to Person. Element Person.communication.preferred has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This language is specifically identified for communicating healthcare information.

People that master multiple languages up to certain level may prefer one or more, i.e. feel more confident in communicating in a particular language making other languages sort of a fall back method. Element Person.communication.preferred is part of an existing definition because parent element Person.communication requires a cross-version extension. Element Person.communication.preferred has a context of Person based on following the parent source element upwards and mapping to Person. Element Person.communication.preferred has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Indicates whether or not the person prefers this language (over other languages he masters up a certain level).

This language is specifically identified for communicating healthcare information.

R5: Person.communication (new:BackboneElement)

Element Person.communication has a context of Person based on following the parent source element upwards and mapping to Person. Element Person.communication has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If no language is specified, this implies that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple Person.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.

Note that this property should not be used to update any linked/logically linked practitioner resources as it serves as a language that can be used to communicate with patients - however it may be used to inform the value on practitioner, along with their role at the organization (with the practitioner's permission)

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Person.communication.language (new:CodeableConcept)

Element Person.communication.language is part of an existing definition because parent element Person.communication requires a cross-version extension. Element Person.communication.language has a context of Person based on following the parent source element upwards and mapping to Person. Element Person.communication.language has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.

Most systems in multilingual countries will want to convey language. Not all systems actually need the regional dialect. Element Person.communication.language is part of an existing definition because parent element Person.communication requires a cross-version extension. Element Person.communication.language has a context of Person based on following the parent source element upwards and mapping to Person. Element Person.communication.language has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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.

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.

The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-AU" for Australian English.

The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.

R5: Person.communication.preferred (new:boolean)

Element Person.communication.preferred is part of an existing definition because parent element Person.communication requires a cross-version extension. Element Person.communication.preferred has a context of Person based on following the parent source element upwards and mapping to Person. Element Person.communication.preferred has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This language is specifically identified for communicating healthcare information.

People that master multiple languages up to certain level may prefer one or more, i.e. feel more confident in communicating in a particular language making other languages sort of a fall back method. Element Person.communication.preferred is part of an existing definition because parent element Person.communication requires a cross-version extension. Element Person.communication.preferred has a context of Person based on following the parent source element upwards and mapping to Person. Element Person.communication.preferred has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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.

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.

Indicates whether or not the person prefers this language (over other languages he masters up a certain level).

This language is specifically identified for communicating healthcare information.

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 for a list).