How can a profile be used to fix the version of the Value Set Definition, rather than the code system? - 2018-Jan Core #305

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Terminology Infrastructure
    • ExpansionProfile [deprecated]
    • Hide

      Both the ValueSet $expand and $validate-code operations now have a valueSetVersion parameter which gives the ability to do this on a type-level operation invocation, and for instance invocation a resource instance with the correct value set definition version can be specified for the operation.

      ExpansionProfile.fixedVersion.system/ExpansionProfile.fixedVersion.version does not reference a value set - it fixes the code system version, not the value set version.

      Show
      Both the ValueSet $expand and $validate-code operations now have a valueSetVersion parameter which gives the ability to do this on a type-level operation invocation, and for instance invocation a resource instance with the correct value set definition version can be specified for the operation. ExpansionProfile.fixedVersion.system/ExpansionProfile.fixedVersion.version does not reference a value set - it fixes the code system version, not the value set version.
    • Rob Hausam/Carmela Couderc: 8-0-0
    • Clarification

      Existing Wording: ExpansionProfile.fixedVersion: how can a profile be used to fix the version of the Value Set Definition, rather than the code system? Or is ExpansionProfile.fixedVersion.system/ExpansionProfile.fixedVersion.version used for a uri that identifies the ValueSet resource containing the specific VSD?

      Summary:

      How can a profile be used to fix the version of the Value Set Definition, rather than the code system?

            Assignee:
            Unassigned
            Reporter:
            Ted Klein
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: