FHIR Chat · R4 SPs contain all the modifiers and comparators etc · conformance

Stream: conformance

Topic: R4 SPs contain all the modifiers and comparators etc

Eric Haas (Feb 19 2019 at 15:42):

I just noticed that in R4 the Search Parameters include all the And/Or, comparators and modifiers ( oh my!). for example:

  {
    "fullUrl" : "http://hl7.org/fhir/SearchParameter/Questionnaire-publisher",
    "resource" : {
      "resourceType" : "SearchParameter",
      "id" : "Questionnaire-publisher",
      "extension" : [{
        "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
        "valueCode" : "trial-use"
      }],
      "url" : "http://hl7.org/fhir/SearchParameter/Questionnaire-publisher",
      "version" : "4.0.0",
      "name" : "publisher",
      "status" : "draft",
      "experimental" : false,
      "date" : "2018-12-27T22:37:54+11:00",
      "publisher" : "Health Level Seven International (FHIR Infrastructure)",
      "contact" : [{
        "telecom" : [{
          "system" : "url",
          "value" : "http://hl7.org/fhir"
        }]
      },
      {
        "telecom" : [{
          "system" : "url",
          "value" : "http://www.hl7.org/Special/committees/fiwg/index.cfm"
        }]
      }],
      "description" : "Name of the publisher of the questionnaire",
      "code" : "publisher",
      "base" : ["Questionnaire"],
      "type" : "string",
      "expression" : "Questionnaire.publisher",
      "xpath" : "f:Questionnaire/f:publisher",
      "xpathUsage" : "normal",
      !"multipleOr" : true,
      !"multipleAnd" : true,
      !"modifier" : ["missing",
      "exact",
      "contains"]
    }
  }

In STU3 these are left out and there was no And/Or. To date, when authoring an IG we have defined the extent of search for each search parameter a server must support in the the cap statements ( see for example US Core ). But now it seems when you support parameter A it is an all or nothing deal. You can't say for example I support the Questionnaire publisher parameter but not the contains modifier. Is this the intent and did we document this?

here is what we say in the profiling page:

"
5.1.0.20 Search Criteria
Implementations can define search criteria in addition to those defined in the specification itself. Search criteria fall into one of four categories:

Enabling search on core elements that don't have standard search criteria defined (e.g. searching Observation by normal range)
Enabling search on elements that already have standard search criteria defined, but with custom matching rules; e.g. a sounds-like search on Practitioner name
Enabling search on an extension
Enabling search that doesn't correspond to a single element but rather a combination of elements or computation on an element; e.g. searching for patients by age

Additional Search Parameters can be defined using the SearchParameter resource.
"

How do we customize ( extend or constrain ) the search criteria in R4? a SHALL, SHOULD, MAY extension? or is it all or nothing ?

Grahame Grieve (Feb 19 2019 at 17:39):

need to put this on FHIR-I agenda @Lloyd McKenzie @Ewout Kramer @Rick Geimer @Josh Mandel

Rick Geimer (Feb 20 2019 at 16:17):

Added to agenda for next meeting:
https://confluence.hl7.org/display/FHIRI/FHIR+Infrastructure+Minutes+CC+20190225

Michael Donnelly (Feb 25 2019 at 20:45):

https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=20470

Last updated: Apr 12 2022 at 19:14 UTC