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

Search should mandate both GET and POST

    XMLWordPrintableJSON

Details

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

      As a short-term measure until CapabilityStatement2 IG is out, we will define an extension with a scope of CapabilityStatement.rest and CapabilityStatement.rest.resource.  In the longer term, this will be handled (potentially w/ more complexity around where each is supported) in CapabilityStatement 2.

      extension will be 0..1 with a type of 'code' with values of "GET", "POST" or "BOTH".  Definition:

      Indicates the type of search mechanism supported by this.

      Comment:

      If not present, it means either - the system chooses to not declare, or the rules for when GET or POST are supported are more complex than can be managed by simply declaring at the resource level.

      Show
      As a short-term measure until CapabilityStatement2 IG is out, we will define an extension with a scope of CapabilityStatement.rest and CapabilityStatement.rest.resource.  In the longer term, this will be handled (potentially w/ more complexity around where each is supported) in CapabilityStatement 2. extension will be 0..1 with a type of 'code' with values of "GET", "POST" or "BOTH".  Definition: Indicates the type of search mechanism supported by this. Comment: If not present, it means either - the system chooses to not declare, or the rules for when GET or POST are supported are more complex than can be managed by simply declaring at the resource level.
    • Gino Canessa/Bas van den Heuvel: 13-0-1
    • Enhancement
    • Compatible, substantive
    • R5

    Description

      Server support for GET and POST search is and should be mandatory.

      The "MAY return a 405 - do not support, try the other one", is a runtime feedback element and should be part of the CapabilityStatement process. But that would break the GET and POST mandatory choice. As a consequence, this escape route should be blocked and all server implementations should be mandated to support GET and POST based search.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: