Observation searches that hit two fields are problematic - 2016-09 core #168

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Orders & Observations
    • Observation
    • 10.1.5
    • Hide

      add the serach params to support capability to do a seach on only .code or .value[x] and only .component.code or component.value[x].

      Show
      add the serach params to support capability to do a seach on only .code or .value [x] and only .component.code or component.value [x] .
    • Eric Haas/Jose Costa-Teixera: 7-0-6
    • Enhancement
    • Compatible, substantive
    • DSTU2

      Comment:

      Several of the Observation search fields are defined to resolve to two elements – one being on the Observation itself and the other being on a component of the Observation. As a result, users must post-process results to determine if their "code" or "value-[x]" searches matched on the direct Observation or on one of its components.

      This can cause further issues when multiple parameters are used. For example a search on "code" and "value-quantity" might contain a result that matches "code" on the Observation but "value-quantity" on one of its components. In this case, "code-value-quantity" might be a better choice, but component parameters don't exist for all possible couplings.

      Please support parameters to reference "code" and "value-[x]" of only the observation, as well as parameters to reference "code" and "value-[x]" of only the components.

      Summary:

      Observation searches that hit two fields are problematic

            Assignee:
            Unassigned
            Reporter:
            cmoesel
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: