Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-44727

Extensions otherName and otherTitle clarification/aligning

    XMLWordPrintableJSON

Details

    • Icon: Technical Correction Technical Correction
    • Resolution: Unresolved
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R5
    • Terminology Infrastructure
    • CodeSystem
      ValueSet

    Description

      There is a misalignment between extensions otherName and otherTitle in CodeSystem and ValueSet resources.

      CodeSystem-otherName:

      https://hl7.org/fhir/extensions/StructureDefinition-codesystem-otherName.html

      1) .name definition mentions ValueSet, not CodeSystem.

      2) By definition, the element is meant for a humanreadable title, not machinefriendly name. Extension has already been renamed for the same reason for ValueSet in https://jira.hl7.org/browse/FHIR-25395

      3) The description text implies the name/title has a language, which it doesn't. It would make sense either to remove the boolean value for "preferred" or to add language attribute. (No preferences here, both have pros and cons.)

      4) If the extension remains a complex extension, consider adding "type" attribute to distinguish, for example, abbreviated titles.

       

      ValueSet-otherName:

      https://hl7.org/fhir/extensions/StructureDefinition-valueset-otherName.html

      The description text implies the name has a language, which it doesn't. It would make sense either to remove the boolean value for "preferred" or to add language attribute. (otherName is for machine processing, so not sure if language is an actual requirement here or a relic from the earlier change (https://jira.hl7.org/browse/FHIR-25395). 

       

      ValueSet-otherTitle:

      https://hl7.org/fhir/extensions/StructureDefinition-valueset-otherTitle.html

      1) The description text implies the title has a language, which it doesn't. It would make sense either to remove the boolean value for "preferred" or to add language attribute.

      2) If the extension remains a complex extension, consider adding "type" attribute to distinguish, for example, abbreviated titles.

      --------

      I would appreciate to start from clarifications, so that we could use (and redesign, if needed) the extensions in our implementation (R5) in a future-proof manner.

      Attachments

        Activity

          People

            Unassigned Unassigned
            rlindstrom Rutt Lindstrom
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: