Tracing of what has been done could be improved by including an ?Action? object as a backbone element in RequestGroup as RequestGroup.activity.outcomeRefence - 2018-May Core STU #19

XMLWordPrintableJSON

    • Type: Comment
    • Resolution: Considered - Question answered
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Clinical Decision Support
    • Clinical Reasoning Module
    • 14.3.0.1.3.1
    • Hide

      This is managed by the instantiates element of the created Request resource, which provides a way to point back to the ActivityDefinition that was used to produce the Request.

      Show
      This is managed by the instantiates element of the created Request resource, which provides a way to point back to the ActivityDefinition that was used to produce the Request.
    • Bryn Rhodes/Thomson Kuhn: 13-0-0

      Existing Wording: Each action may specify the type of action to perform:

      ? Create

      ? Update

      ? Remove

      ? Fire Event

      The Create, Update, and Remove actions indicate that particular resources should be created, updated, or removed, and the Fire Event action indicates that a particular named event should be triggered.

      Comment:

      Tracing of what has been done could be improved by including an ?Action? object as a backbone element in RequestGroup as RequestGroup.activity.outcomeRefence

      Action:

      source ? Reference( resource ) ?target of action

      target ? resource result of RG action.,

      Type ? create-update-remove-fireEvent

      Summary:

      Tracing of what has been done could be improved by including an ?Action? object as a backbone element in RequestGroup as RequestGroup.activity.outcomeRefence

            Assignee:
            Unassigned
            Reporter:
            Bas van den Heuvel
            Bas van den Heuvel
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: