FHIR Extensions Pack, published by HL7 International / FHIR Infrastructure. This guide is not an authorized publication; it is the continuous build for version 5.3.0-ballot-tc1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-extensions/ and changes regularly. See the Directory of published versions
| Official URL: http://hl7.org/fhir/ValueSet/language-preference-type | Version: 5.3.0-ballot-tc1 | |||
| Standards status: Trial-use | Maturity Level: 3 | Responsible: HL7 International / Patient Administration | Computable Name: LanguagePreferenceType | |
| Other Identifiers: OID:2.16.840.1.113883.4.642.3.1022 | ||||
This value set defines the set of codes for describing the type or mode of the patient's preferred language.
References
Changes since version 5.2.0:
Last updated: 2023-01-31 07:07:38+1100
Profile: Shareable ValueSet
http://hl7.org/fhir/language-preference-type version 📦5.3.0-ballot-tc1| Code | Display | Definition | 
| verbal | verbal | The patient prefers to verbally communicate with the associated language. | 
| written | written | The patient prefers to communicate in writing with the associated language. | 
Expansion performed internally based on codesystem language preference type code system v5.3.0-ballot-tc1 (CodeSystem)
This value set contains 2 concepts
| System | Code | Display (en) | JSON | XML | 
| http://hl7.org/fhir/language-preference-type | verbal | verbal | ||
| http://hl7.org/fhir/language-preference-type | written | written | 
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies | 
| System | The source of the definition of the code (when the value set draws in codes defined elsewhere) | 
| Code | The code (used as the code in the resource instance) | 
| Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application | 
| Definition | An explanation of the meaning of the concept | 
| Comments | Additional notes about how to use the code |