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

Add action.participant.function to PlanDefinition

    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:
      Clinical Decision Support
    • Related Artifact(s):
      PlanDefinition
    • Resolution Description:
      Hide

      We will add PlanDefinition.actor (0..*) defined as:
      " individual or group involved in the execution of the defined set of activities"
      with the following properties:

      • (inherited id from Element)
      • label 0..1 string - descriptive label for the actor
      • description 0..1 markdown - description of how the actor fits into the overall workflow of the plan definition
      • options 1..* - The characteristics of the candidates that could serve as the actor
           - type 1..1 code - as per existing participant.type
           - role 0..1 CodeableConcept - refines the characteristics of the specified resource type.  Usage note: generally not specified if type='patient'

      We will revise PlanDefinition.participant to have the following properties

      • actor 1..1 string - reference to the 'id' element of the actor who will participate in this action
      • function 0..1 CodeableConcept - indicates how the actor will be involved in the action - author, reviewer, witness, etc.
      Show
      We will add PlanDefinition.actor (0..*) defined as: " individual or group involved in the execution of the defined set of activities" with the following properties: (inherited id from Element) label 0..1 string - descriptive label for the actor description 0..1 markdown - description of how the actor fits into the overall workflow of the plan definition options 1..* - The characteristics of the candidates that could serve as the actor    - type 1..1 code - as per existing participant.type    - role 0..1 CodeableConcept - refines the characteristics of the specified resource type.  Usage note: generally not specified if type='patient' We will revise PlanDefinition.participant to have the following properties actor 1..1 string - reference to the 'id' element of the actor who will participate in this action function 0..1 CodeableConcept - indicates how the actor will be involved in the action - author, reviewer, witness, etc.
    • Resolution Vote:
      Bas van den Heuvel/Floyd Eisenberg: 31-0-1
    • Change Category:
      Enhancement
    • Change Impact:
      Compatible, substantive

      Description

      As discussed in the Workflow call, we should consider adding a "function" to PlanDefinition.action.participant, which will express what function does the participant have in that action, e.g. "receiver", "initiator", or possibly others like "broadcaster"...

      The discussion is held in Workflow calls, and the example that is being worked on is here:

      https://confluence.hl7.org/display/FHIRI/Workflow+Conformance+example

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              costateixeira Jose Costa-Teixeira
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: