Need more details around the differences and uses of .compose and .expansion - 2018-Jan Core #131

XMLWordPrintableJSON

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

      The additional suggested text does not seem to add clarity here. Instead will add a hyperlink to the element definition for .expansion to the 4.8.7 Value Set Expansion section.

      Show
      The additional suggested text does not seem to add clarity here. Instead will add a hyperlink to the element definition for .expansion to the 4.8.7 Value Set Expansion section.
    • Rob Hausam/Carmela Couderc: 5-0-0
    • Enhancement
    • Non-substantive
    • Yes
    • STU3

      Existing Wording: .expansion: The list of codes that are actually in the value set under a given set of conditions ("extension")

      Proposed Wording: .expansion: The complete list of codes that are in the value set ("extension"). The .expansion is typically derived from the definition in .compose. The .expansion is not typically stored in the resource on the server, but automatically generated using the $expand operation. If the .expansion is stored on the server with the value set, it should only be returned when asking for the correct criteria using the $expand operation.

      Comment:

      Need more details around the differences and uses of .compose and .expansion

      Summary:

      Need more details around the differences and uses of .compose and .expansion

            Assignee:
            Unassigned
            Reporter:
            Sean McIlvenna
            Sean McIlvenna
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: