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

Clarify scope of collection passed to union()

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIRPath (FHIR)
    • 1.0 [deprecated]
    • Implementable Technology Specifications
    • (NA)
    • Hide

      Update the example illustrating synonymy of union and | to use `x` and `y` rather than `a` and `b`, to make clear that is a completely separate example from the previous one illustrating union behavior.

      Add the proposed example, as a third example and use it to clarify that union does not introduce an iteration context.

      Show
      Update the example illustrating synonymy of union and | to use `x` and `y` rather than `a` and `b`, to make clear that is a completely separate example from the previous one illustrating union behavior. Add the proposed example, as a third example and use it to clarify that union does not introduce an iteration context.
    • Bryn Rhodes/Joseph Shook: 4-0-0
    • Enhancement
    • Non-substantive

    Description

      The example in https://hl7.org/fhirpath/#unionother-collection introduces collections "A" and "B" (in uppercase, which is odd), and then uses them in an expression as "a" and "b", without providing information about where "a" and "b" are coming from. This caused some confusion-- see https://chat.fhir.org/#narrow/stream/179266-fhirpath/topic/Context.20for.20.60.2Eunion.60. In that thread, a more clear example was given, namely that for a Patient resource as the context, ```name.select(use.union(given))``` is the same as ```name.select(use | given)```. I suggest changing the example to that one.

      Attachments

        Activity

          People

            Unassigned Unassigned
            plynch Paul Lynch
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: