Documentation of Search Modifiers unclear / misleading

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • Search
    • 2.21.1.4.4
    • Hide

      Will apply #1

      For #2, will change "left matches" to "left-matches" and will add an example.

      Show
      Will apply #1 For #2, will change "left matches" to "left-matches" and will add an example.
    • Grahame Grieve/Ewout Kramer: 2-0-0
    • Enhancement
    • Non-substantive
    • STU3

      Two phrases in the documentation on search modifiers are unclear or misleading...

      1) (existing) For string: :exact (the match needs to be exact, no partial matches, case sensitive and accent-sensitive), or :contains (case insensitive and accent-insensitive, partial match at start or end), instead of the default behavior (case insensitive and accent-insensitive, partial matches at the end of the string).

      I think the underlined words should be replaced with search text matched anywhere in the string and beginning

      2) (existing) For uri: :below, :above indicate that instead of an exact match, either the search term left matches the value, or vice-versa.

      Typo, should be indicates, and 'search term left' just doesn't mean anything. I read through the rest of the page to try and understand how this is used, but didn't find an example of using :above or :below for URI (it is shown for terminology subsumption, but I think that's a different deal).

            Assignee:
            Unassigned
            Reporter:
            john.s.carter
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: