Clarify distinction between ElementDefinition.defaultValue vs. ElementDefinition.meaningWhenMissing

XMLWordPrintableJSON

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

      Add examples of Period.end and Quantity.comparator and ValueSet.define.concept.abstract to the definition. Note that defaultValue is preferred over meaningWhenMissing.

      Note: check why meaningWhenMissing isn't appearing in the profiles

      Show
      Add examples of Period.end and Quantity.comparator and ValueSet.define.concept.abstract to the definition. Note that defaultValue is preferred over meaningWhenMissing. Note: check why meaningWhenMissing isn't appearing in the profiles
    • Grahame / Josh: 8-0-0
    • Enhancement
    • Non-substantive
    • DSTU1 [deprecated]

      The definitions of ElementDefinition.defaultValue and ElementDefinition.meaningWhenMissing appear very similar:

      d efaultValue The value that should be used if there is no value stated in the instance.

      *meaningWhenMissing * The Implicit meaning that is to be understood when this element is missing.

      I assume that these both exist for different purposes, but I can't figure out what those different purposes are. If both are needed, then each should definitino refer to the other and directly explain what the difference is.

            Assignee:
            Unassigned
            Reporter:
            Josh Mandel
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: