_filter operators lack sufficient detail for implementation

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • Normative
    • Search
    • 3.1.3.2
    • Hide

      This content:
      - did not change from May to Sept. ballot (and thus is out of scope)
      - is STU, not Normative (and thus is out of scope)
      - has not yet been widely implemented and may still evolve.

      We welcome suggestions on how to improve the clarity of the documentation. If received in sufficient time, we'll consider for inclusion in R4, but we do not have the bandwidth to develop improved guidance ourselves in this timeframe. If not, please resubmit as an issue for consideration in R5 where it will definitely be addressed.

      Show
      This content: - did not change from May to Sept. ballot (and thus is out of scope) - is STU, not Normative (and thus is out of scope) - has not yet been widely implemented and may still evolve. We welcome suggestions on how to improve the clarity of the documentation. If received in sufficient time, we'll consider for inclusion in R4, but we do not have the bandwidth to develop improved guidance ourselves in this timeframe. If not, please resubmit as an issue for consideration in R5 where it will definitely be addressed.
    • Mike Henderson/Rick Geimer: 31-0-3
    • Enhancement

      These operators have no analog in SQL and HQL. Therefore, we need clear explanation such that implementers can adopt them consistently.

      Implementers need additional explanation and example expressions using these FHIR-specific operators for _filter :

      *pr *The set is empty or not (value is false or true)

      po True if a (implied) date period in the set overlaps with the implied period in the value

      *ss *True if the value subsumes a concept in the setsbTrue if the value is subsumed by a concept in the setinTrue if one of the concepts is in the nominated value set by URI, either a relative, literal or logical vs

      *ni *True if none of the concepts are in the nominated value set by URI, either a relative, literal or logical vs

      re True if one of the references in set points to the given URL

            Assignee:
            Unassigned
            Reporter:
            Ioana Singureanu
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: