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

PlanDefinition Cancer Example Subaction

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Resolved - change required (View Workflow)
    • Priority: Medium
    • Resolution: Persuasive with Modification
    • Specification:
      US Making EHR Data More available for Research and Public Health (MedMorph) (FHIR)
    • Raised in Version:
      0.1.0
    • Work Group:
      Public Health
    • Related Artifact(s):
      Plan Definition example for Cancer Reporting
    • Grouping:
    • Resolution Description:
      Hide

      We will need to model composite actions such as Validate and Submit together. Another example is checking Reportability and if it is reportable, creation of a report all in one action. In order to achieve this we will mark the action.action as Must Support.  To the extent possible we will not use the sub-action until actually required. 

      For the cancer example, we will eliminate the sub-action and use the top level action itself.

      Show
      We will need to model composite actions such as Validate and Submit together. Another example is checking Reportability and if it is reportable, creation of a report all in one action. In order to achieve this we will mark the action.action as Must Support.  To the extent possible we will not use the sub-action until actually required.  For the cancer example, we will eliminate the sub-action and use the top level action itself.
    • Resolution Vote:
      Kishore Bashyam / Craig Newman : 28 - 0 - 1
    • Change Category:
      Correction
    • Change Impact:
      Compatible, substantive

      Description

      The check-trigger-codes example in the PlanDefinition for Cancer Reporting uses a nested sub action to define the action code. Is there a reason this is a sub action? Since PlanDefinition.action.action is not flagged as must support, I propose the action should only be included in the PlanDefinition.action.

        Attachments

          Activity

            People

            Assignee:
            nageshbashyam Nagesh Bashyam
            Reporter:
            blangley Benjamin Langley
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Vote Date: