Search API doesn't work well for population health - 2016-09 core #167

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • FHIR Infrastructure
    • Search
    • 2.42.1
    • Hide

      We find this non-persusative. We acknowledge that population health queries are an important use case, but we don't think that FHIR's search API is the right place to attach this functionality. Instead, we think this functionality fits best into a dedicated query language (e.g. CQL).

      Show
      We find this non-persusative. We acknowledge that population health queries are an important use case, but we don't think that FHIR's search API is the right place to attach this functionality. Instead, we think this functionality fits best into a dedicated query language (e.g. CQL).
    • Kevin Shekleton / Chris Grenz: 6-0-0
    • Enhancement

      Comment:

      The FHIR search API does not lend itself well to some population health type queries. Some of these limitations are already being considered/addressed (e.g., "_has" parameter).

      One important capability that is currently missing is the ability to search on a most recent value. For example, search for patients whose MOST RECENT blood pressure reading is > x. We can perform a search on Observation, with _revinclude to get the patient, but that search will go against ALL the patient's BP observations, not just the most recent.

      This is likely tricky to design and implement, but it's probably worth the effort.

      Summary:

      Search API doesn't work well for population health

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

              Created:
              Updated:
              Resolved: