CodeSystem.filter.description and CodeSystem.property.description

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Terminology Infrastructure
    • Normative
    • CodeSystem
    • Hide

      There does not seem to be a need for the additional representation capabilities of markdown at the levels of 'filter' and 'property' within the resource, which would be required to make this consistent across all three 'description' elements. Making this change would likely not be worth the cost to the implementers.

      Show
      There does not seem to be a need for the additional representation capabilities of markdown at the levels of 'filter' and 'property' within the resource, which would be required to make this consistent across all three 'description' elements. Making this change would likely not be worth the cost to the implementers.
    • Grahame Grieve / Peter Jordan: 6-0-0
    • Correction

      CodeSystem.filter.description and CodeSystem.property.description

      The data type = string. However CodeSystem.description data type = markdown

      Either all description elements should be of same data type, or the element name should change. See below.

      The definition of the property.description and filter.description elements is: why the property is defined, and/or what it conveys _and how or why the filter is used which is very similar to the wording of CodeSystem.purpose (_why this code system is defined).

      Should the two description elements of interest in this ticket be named purpose instead of description

            Assignee:
            Unassigned
            Reporter:
            Carmela Couderc
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: