Stream: IG creation
Topic: Search Parameters
Lisa Nelson (Jan 25 2020 at 22:51):
@Lloyd McKenzie @Sean McIlvenna Where are we supposed to be documenting expectations about what Search Parameters SHALL, SHOULD, or MAY be supported?
Lloyd McKenzie (Jan 25 2020 at 22:51):
CapabilityStatement
Lisa Nelson (Jan 25 2020 at 22:53):
@Lloyd McKenzie In US Core I see documentation about which search parameters are Required and which are Optional. Would we also do something like this in the Profile?
Lloyd McKenzie (Jan 25 2020 at 22:58):
That information doesn't live in (or belong in) the profile. Not sure why US Core is publishing it there. For example, in US Core there are 3-4 profiles on Observation, but you can't declare search criteria on a per profile basis, only for Observation as a whole. It's not possible to have different criteria for searching lab results than you have for searching smoking data.
Sean McIlvenna (Jan 27 2020 at 23:09):
I suspect you're referring to this: https://www.hl7.org/fhir/us/core/StructureDefinition-us-core-careplan.html#quick-start
Sean McIlvenna (Jan 27 2020 at 23:12):
While CapabilityStatement definitely should be used to assert what SearchParameters are required to be supported, CapabilityStatement is not going to be able to express the requirements defined the way they are in us-core.. For example, you can say in CapabilityStatement "search parameter X is required" and "search paramater Y is required" but you can't say "must support a combination of search parameter x and y"
Sean McIlvenna (Jan 27 2020 at 23:12):
so, that's a little tricky...
Grahame Grieve (Jan 27 2020 at 23:32):
http://hl7.org/fhir/StructureDefinition/capabilitystatement-search-parameter-combination
Eric Haas (Jan 28 2020 at 00:08):
See how it is done in US Core - CapabilityStatements. I used this narrative generator
that will expose it all in the capabiigtystatement narrative including the supported searches. : you upload your capstatement.json (scrub the text element first !) file and run the Jupyter script. ( need to doco how that is done) and presto a pretty new narrative to download. (public site so is read only).
Eric Haas (Jan 28 2020 at 00:10):
The profile pages in us core have extra content before and after profile narrative so that there is plenty of context and notes how to use them. Lloyd's concerns are unwarranted.
Igor Sirkovich (Jan 28 2020 at 00:10):
@Sean McIlvenna You can see examples of use of this extension in the US Core Capability statement
Eric Haas (Jan 28 2020 at 00:12):
All the search criteria for each profile in US Core are described for the benefit of the reader. For the benefit of the testers and servers they are formally described in the Cap statements per resource.
Last updated: Apr 12 2022 at 19:14 UTC
