forcast elements are confusing - STU #219

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Public Health
    • ImmunizationRecommendation
    • Hide

      We don't feel it's appropriate to create a backbone element because we try to stay in line with the Request workflow pattern which does not put requestStatus and requestStatusReason under a backbone elements. These elements are fully homologous, but they are similar enough that we try to follow the request pattern format.

      We prefer the the current element names as they reflect the status of the recommendation. The recommendation is based on the evaluation but it's not conveying an evaluation status per se (an evaluation must always be "completed" in order to generate a recommendation).

      Show
      We don't feel it's appropriate to create a backbone element because we try to stay in line with the Request workflow pattern which does not put requestStatus and requestStatusReason under a backbone elements. These elements are fully homologous, but they are similar enough that we try to follow the request pattern format. We prefer the the current element names as they reflect the status of the recommendation. The recommendation is based on the evaluation but it's not conveying an evaluation status per se (an evaluation must always be "completed" in order to generate a recommendation).
    • Craig Newman/Joginder Madra: 10-0-0
    • Clarification

      Existing Wording: ImmunizationRecommendation.recommendation.forecastStatus:

      Indicates the patient status with respect to the path to immunity for the target disease

      ImmunizationRecommendation.recommendation.forecastReason:

      The reason for the assigned forecast status

      Proposed Wording: Suggestion:

      (1) Create a new "statusEvaluation" cluster or backbone element for these two data elements

      (2) Rename them to: evaluatedStatus and evaluatedStatusReason

      (3) change definition to: indicate assessed status of patient's vaccination, e.g. due, overdue, complete

      Comment:

      Element names and definition/description names are extremely confusing. If readers do not navigate to the value set example codes (due, overdue, immune, contraindicated, complete), the reader is completely at lost regarding what these elements are and their intended use

      Suggestion:

      (1) Given the value set, these two elements do not below to the Recommendation cluster/backbone element. They should form a separate cluster - "statusEvaluation"

      (2) The element names and definition need to be improved

      Summary:

      forcast elements are confusing

            Assignee:
            Unassigned
            Reporter:
            Stephen Chu
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: