Stream: fhir/infrastructure-wg
Topic: GF#16361 - searching canonicals
Grahame Grieve (Jul 02 2018 at 23:16):
I find the disposition of GF#16361 very confusing. it says:
- document how searching canonicals with search type URI
- ensure that canonicals always have a search type of Reference (e.g. not URI)
uh? @Josh Mandel @Christiaan Knaap
Josh Mandel (Jul 02 2018 at 23:19):
In the issue resolution I see something different:
Resolution:
- Clean up the narrative about canonical and version from at "uri" search parameter (http://build.fhir.org/search.html#uri), to read:
"Note that for uri search parameters that search the canonical urls of conformance resources (e.g. StructureDefinition.url, ValueSet.url, etc), servers SHOULD support searching by Canonical URLs, and SHOULD support automatically detecting a |[version] portion, and interpreting that portion as a search on the version element of such conformance resources."
- Make sure that all search parameters that search on elements of type 'canonical' are using the search type "reference".
- Explain somewhere (at the definition of canonical?) why Conformance.url itself is not a canonical.
- Correct the sentence "_tag, _profile and _security parameters are all token types (see below)." in http://hl7.org/fhir/search.html#profile,since _profile is a canonical, thus searched by a reference search type
- The section on Reference search parameters is already substantial and should additionally talk about using [|version] (and business versions). Since there is already narrative on _history "versioned references", this might quickly become confusing to the reader. We suggest splitting up this section in several parts: 1) text relevant to both canonicals and References, 1) text specific to references (like _history) and 2) text specific to canonicals. And be carelful not to use the phrase "version specific", so we better use "canonical with version" or "reference with _history" or somesuch.
Josh Mandel (Jul 02 2018 at 23:20):
There is a distinction between search parameters that index on canonical URLs like StructureDefinition.url (datatype: uri, search parameter type: uri)
Josh Mandel (Jul 02 2018 at 23:21):
... and search parameters that index on elements of type "canonical" (datatype: canonical, search parameter type: reference)
Josh Mandel (Jul 02 2018 at 23:22):
Does this help?
Grahame Grieve (Jul 02 2018 at 23:30):
oh, duh.
Grahame Grieve (Jul 03 2018 at 00:04):
dose anyone know why this is labelled as non-compatible? I think it's not substantiative...
Lloyd McKenzie (Jul 03 2018 at 00:17):
Changing the search types would be non-compatible
Grahame Grieve (Jul 03 2018 at 00:22):
There was none to change
Ewout Kramer (Jul 03 2018 at 08:25):
I think we had found that "Make sure that all search parameters that search on elements of type 'canonical' are using the search type "reference" would result in a change.
Christiaan Knaap (Jul 03 2018 at 10:16):
As the issue already mentions _profile search parameters changes from search type Token to Reference. I think that is a change for most users.
Last updated: Apr 12 2022 at 19:14 UTC
