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

search does not clearly define the timing of the search

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Highest Highest
    • FHIR Core (FHIR)
    • R5
    • FHIR Infrastructure
    • STU
    • REST (http)
      Search
    • Hide

      Not all servers will support a frozen snapshot and we can't make them do so.  However, we will make more explicit in the http#paging section that server behavior on this point can and will vary.  We will also create a tracker item against the forthcoming CapabilityStatement2 IG to define a mechanism for a server to declare whether it has snapshot behavior or not.

      Show
      Not all servers will support a frozen snapshot and we can't make them do so.  However, we will make more explicit in the http#paging section that server behavior on this point can and will vary.  We will also create a tracker item against the forthcoming CapabilityStatement2 IG to define a mechanism for a server to declare whether it has snapshot behavior or not.
    • Grahame Grieve/Josh Mandel: 13-0-0
    • Clarification
    • Non-substantive
    • R5

    Description

      Section 3.2.1.10 Search Result Currency of search seems to suggest that a search result represents the set at the time the search operation executed. So in the case of paged results, the complete set represents the search result at the time of querying.

      Although this is exactly the behavior I expect, it does not seem to be specified clearly by the specification.

      Please add a hard requirement that this is the case.

      Attachments

        Activity

          People

            Unassigned Unassigned
            bvdh Bas van den Heuvel
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: