Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-25210

CarePlan activity-date search param maps string to date

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Applied (View Workflow)
    • Priority: Medium
    • Resolution: Persuasive with Modification
    • Specification:
      FHIR Core (FHIR)
    • Raised in Version:
      STU3
    • Work Group:
      Patient Care
    • Related Artifact(s):
      CarePlan
    • Resolution Description:
      Hide

      1) update activity-date to be activity-scheduled-date and update search param expression to be:

      CarePlan.activity.detail.scheduled.as(Timing) | CarePlan.activity.detail.scheduled.as(Period)

      2) add a new search param, activity-scheduled-string

      CarePlan.activity.detail.scheduled.as(string)

      Show
      1) update activity-date to be  activity-scheduled-date  and update search param expression to be: CarePlan.activity.detail.scheduled.as(Timing) | CarePlan.activity.detail.scheduled.as(Period) 2) add a new search param,  activity-scheduled-string CarePlan.activity.detail.scheduled.as(string)
    • Resolution Vote:
      Emma Jones / Rob Hausam : 4-0-1
    • Change Category:
      Correction
    • Change Impact:
      Non-compatible

      Description

      According to http://build.fhir.org/search.html#table the data type 'string' should map to search parameters of type 'string' or 'token'.

      However, the CarePlan resource has a search parameter of type 'date' named activity-date and this has an expression like "CarePlan.activity.detail.scheduled" which selects an element that can be a string (or a Timing or Period).

      I suggest updating the search parameter expression to only select this element when its of type decimal (e.g. "CarePlan.activity.detail.scheduled as Period | CarePlan.activity.detail.scheduled as Timing")

      Note: https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=25173 identifies a different search parameter with the same issue (mapping string element to a date search parameter). if some global guidance is given in the search section, then maybe the expressions can stay as-is.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              michelle.m.miller Michelle Miller
              Reporter:
              lmsurprenant Lee Surprenant
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: