Add language to HumanName - 2016-09 core #569

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Modeling & Methodology
    • Datatypes
    • 2.22.0.12
    • Hide

      Already have a 21090 language extension (iso21090-ST-language) for string, which can be used on each of the name parts. This is how the requirement is supported in v3 and allows intermixing of languages within a single name. Given that the notion of language at the full name level isn't supported in v2 or v3 and that we can support it at the part level, reluctant to add two different ways of conveying languages for names.

      Also see the comments below which can be used for some of these use-cases.

      Show
      Already have a 21090 language extension ( iso21090-ST-language ) for string, which can be used on each of the name parts. This is how the requirement is supported in v3 and allows intermixing of languages within a single name. Given that the notion of language at the full name level isn't supported in v2 or v3 and that we can support it at the part level, reluctant to add two different ways of conveying languages for names. Also see the comments below which can be used for some of these use-cases.
    • Grahame Grieve/Ron Shapiro: 3-0-0
    • Enhancement

      Comment:

      HumanName: add language 0..1 code

      {ISO 3166-1}

      to allow for explicit detailing of the language of the name as one cannot definitively determine the language from examining the characters used (eg. Hawaiian). Alternately see below.

      Summary:

      Add language to HumanName

            Assignee:
            Unassigned
            Reporter:
            Paul Knapp
            Paul Knapp
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: