When an event is triggered within the FHIR repo, what will happen? - 2018-May Core STU #21

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Clinical Decision Support
    • Clinical Reasoning Module
    • 14.3.0.1.3.2
    • Hide

      For triggered PlanDefinitions, the event means the PlanDefinition apply process should be performed. How that actually happens within an implementation is not prescribed.

      Add this note to the documentation here.

      Show
      For triggered PlanDefinitions, the event means the PlanDefinition apply process should be performed. How that actually happens within an implementation is not prescribed. Add this note to the documentation here.
    • Bryn Rhodes/Thomson Kuhn: 13-0-0
    • Enhancement
    • Non-substantive
    • STU3

      Existing Wording: Each action may have any number of triggers associated to indicate what events should trigger the action to be taken. The following types of triggers may be defined:

      ? Named Event

      ? Scheduled Event

      ? Data Event

      Comment:

      When an event is triggered within the FHIR repo, what will happen? Will the PD be run with no Patient or Encounter context?

      Where will the resulting Careplan go?

      Alternative ? limit to CDS Hooks named-events?

      When only inspected when run ? other checks can be done in the context of the condition check.

      Summary:

      When an event is triggered within the FHIR repo, what will happen?

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

              Created:
              Updated:
              Resolved: