Tooling should enforce coding capitalization consistency

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Terminology Infrastructure
    • STU
    • (NA)
    • Hide

      The standard is lowercase codes with dashes as separators, and title case display names.

      Some code systems differ from this for particular reasons, and are allowed to do so if confirmed with Vocab or MnM.

      The tool will require this for all non-approved code systems.

      Show
      The standard is lowercase codes with dashes as separators, and title case display names. Some code systems differ from this for particular reasons, and are allowed to do so if confirmed with Vocab or MnM. The tool will require this for all non-approved code systems.
    • Richard Etterna / Andy Stechishin: 4-0-0
    • Enhancement
    • Non-compatible
    • DSTU1 [deprecated]

      When WGs define vocabularies, they're sometimes inconsistent with the capitalization of either the codes or display names. (It's possible there could also be variation between the use of camelCase and dashes, though I don't have an example of that.) If we're not going to have a standard that says "always lower case" or "always upper-case" or "always UpperCamelCase", then the tooling should at least enforce consistency amongst the codes within each FHIR-defined code system.

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: