Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-42330

Clarify interpretation intersection include rule

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • Shorthand (FHIR)
    • 2.0.0
    • FHIR Infrastructure
    • Language Reference
    • 3.5.12
    • Hide

      We will fix the syntax coloring to ensure that the syntax is valid when all optional parts are removed.

      We will also update the first bullet in notes so that it reads:

      When a single include rule includes more than one item (code system or value set), the applicable codes are those present in all listed items (i.e., the intersection).

      Last, we will add a sentence like the following:

      For additional details about ValueSet composition, see the FHIR documentation on ValueSet composition rules.

      Show
      We will fix the syntax coloring to ensure that the syntax is valid when all optional parts are removed. We will also update the first bullet in notes so that it reads: When a single include rule includes more than one item (code system or value set), the applicable codes are those present in all listed items (i.e., the intersection). Last, we will add a sentence like the following: For additional details about ValueSet composition, see the FHIR documentation on ValueSet composition rules .
    • Chris Moesel/Gino Canessa: 14-0-2
    • Clarification
    • Non-substantive

    Description

      "system

      {CodeSystem}" is in red, indicating that it is optional, however the syntax doesn't work if those elements are omitted (results in "codes from and valueset…").

      Also it is unclear whether the result of listing multiple valuesets their union or intersection, which is then joined (interection) with the nominated codesystem. It may be easier to define the behavior by deferring to the FHIR spec.

      h3. Existing Wording:
      * include codes from system {CodeSystem}

      |

      {version string}

       and valueset

      {ValueSet1}

      |

      {version1 string}

       and

      {ValueSet2}

      |

      {version2 string}

      ...

      (Comment 51 - imported by: Ron G. Parker)

      Attachments

        Activity

          People

            Unassigned Unassigned
            Rongparker Ron G. Parker
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: