clarify the purpose and source of ValueSet.version when 'compose' is not present

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Terminology Infrastructure
    • ValueSet
    • Hide

      When available, ValueSet.status and ValueSet.version from the ValueSet resource instance which contains the definition SHALL be persisted to the ValueSet resource instance which contains the expansion. 

      Show
      When available, ValueSet.status and ValueSet.version from the ValueSet resource instance which contains the definition SHALL be persisted to the ValueSet resource instance which contains the expansion. 
    • Rob Hausam/Carmela Couderc: 9-0-0
    • Enhancement
    • Non-substantive

      It has been unclear what should be used to populate ValueSet.version in the case of a ValueSet resource instance containing only an 'expansion' element without a 'compose' (i.e. a "naked expansion"). To clarify this, we need to add guidance to the http://build.fhir.org/valueset.html#expansion and http://build.fhir.org/valueset-operation-expand.html pages that states explicitly that ValueSet.version SHALL always be populated with the value of ValueSet.version obtained from the ValueSet resource instance (including a 'compose' element) that was used as the basis for the expansion (i.e. when the $expand operation was performed).

      The ValueSet resource is normative, we will inform and solicit feedback from the implementer community on this clarification (i.e. Zulip implementer and terminology streams).

            Assignee:
            Unassigned
            Reporter:
            Robert Hausam
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: