Stream: implementers
Topic: US core smoking status search parameters
Weiyu Zhang (May 21 2020 at 19:51):
The US core capabilitystatement narrative defines patient+code, patient+category+date, and patient+category as required search parameter combinations for Observation. However, the smoking status profile only defines patient+code as the sole required search parameter combination.
Just to confirm, is the search parameter list on the capabilitystatement narrative the superset of all required search parameter combinations across all profiles (and mandatory search parameters defined in each profile are the only required combinations), or are patient+category+date and patient+category required for smoking status observations as well?
Eric Haas (May 21 2020 at 21:17):
There is not really a way to differentiate search parameters by profile in the CapabilityStatements and last time I checked with implementers they did not narrow support of search parameters by profile just to the resource level so in essence yes you could search smoking status by all three. However, I doubt that certification will even look at the full set of Observation search capability for smoking status especially since category and effective is undefined in the profile.
Robert Scanlon (May 22 2020 at 03:23):
Is there expected behavior for the case where a system does not have any support for the category element for smoking status but a client searches by patient+category? Can they ignore it and just return everything for that patient (and return an appropriate self url in the search bundle reflecting that behavior)? Can they interpret category as null in their system and simply not return anything at all?
Robert Scanlon (May 22 2020 at 03:26):
Fortunately this appears to be the only time that a profile doesn't require support for all the elements associated w/required search parameters in the capability statement (by 'require support for' i mean with the must support flag or min cardinality of > 0).
Robert Scanlon (May 22 2020 at 03:30):
Though I think the two Pediatric profiles are missing mandatory searches in the quick start section: https://www.hl7.org/fhir/us/core/StructureDefinition-pediatric-bmi-for-age.html#quick-start
Lloyd McKenzie (May 22 2020 at 03:31):
It's totally fine to ignore search criteria - so long as you declare what you actually execute in the search link. (If you like belt + suspenders, you can also include a warning operation outcome in the search response Bundle)
Eric Haas (May 22 2020 at 20:30):
Though I think the two Pediatric profiles are missing mandatory searches in the quick start section
It is documented to refer to the FHIR Vital Signs Quick Start section for how to search by vital signs.
Eric Haas (May 22 2020 at 20:33):
It's totally fine to ignore search criteria - so long as you declare what you actually execute in the search link.
its not fine when the Capability statement says support is required. So the servers need to support across the type. But if the resources elements are empty you will get no results. It is on the user to understand this.
Eric Haas (May 22 2020 at 20:35):
The profile Quick Start provide profile specific guidance and omits the searches that are not useful.
Eric Haas (May 22 2020 at 20:37):
If anyone feels this constitutes and omission/errata and deserves a clarifying note. log a tracker
Last updated: Apr 12 2022 at 19:14 UTC
