Generated from smart-base/L4/processes/act-on-decision-support.bpmn by gen-processes-viz.ts — do not edit here. All processes · smart-base processes

Act on decision-support guidance

Process_ActOnDecisionSupport · advisory · 4 step(s)

The point-of-care system applies one of the DAK’s decision tables, published as a CPG-on-FHIR PlanDefinition, to one client ($apply) and shows the health worker what it proposes (a RequestGroup, or CDS Hooks cards). The health worker accepts or declines each action, one tap each, and the system makes the accepted requests active in the client’s CarePlan; a declined action is never written. Recording why is OPTIONAL and never blocks: Event_AddReason is a non-interrupting boundary event on the review. It happens only when the health worker taps “add a reason” while reviewing, starts the rationale task beside the review, and takes nothing away from it: the review completes and the care plan is updated whether or not a reason is ever recorded. Skipping is the default, because the event is absent unless chosen. The record, when made, is one FHIR Provenance. Skills: apply-decision-support, review-decision-support-guidance, record-decision-rationale, activate-accepted-guidance (package authoring-who-smart-guidelines).

BPMN diagram: Act on decision-support guidance

How it connects

  • Called by: no call activity names this process
  • Calls: none
  • Presented on: no docs page section shows this diagram
  • Running instances: none recorded

Lanes — who acts

lanerolewhat it does here
Point-of-care systempoint-of-care-systemThe app or EHR: applies the PlanDefinition and writes what the health worker accepted. Decides nothing clinical.
Health workerhealth-workerA person in the health-worker role: accepts or declines the guidance and stays accountable for the care given. Never required to say why.

Steps

Every one of the 4 step(s) is documented.

steplaneskill / sub-processwhat it does
Apply the PlanDefinition
Task_Apply
Point-of-care systemapply-decision-supportPlanDefinition/$apply for this client (or a CDS Hooks call): every proposed request is a draft proposal, and nothing is written to the record.
Accept or decline the guidance
Task_Review
Health workerreview-decision-support-guidanceSee the proposed actions on the device and accept or decline each one, one tap each (“accept all” is one tap); modify one only where the device offers it. Nothing else is asked; an “add a reason” link is shown, never required.
Update the care plan
Task_Activate
Point-of-care systemactivate-accepted-guidanceMake each accepted request active (intent plan or order) and reference it from the client’s CarePlan, in one transaction; write nothing for a declined action.
Note the reason (optional)
Task_Rationale
Health workerrecord-decision-rationaleOptional: pick a coded reason or type one, or neither; one FHIR Provenance records who decided what about which guidance, and why. Never required, never waited for.

Decisions

Every one of the 2 decision(s) is documented.

decisionwhat decides itbranches
Anything proposed?
Gateway_HasGuidance
Read from the result: an empty RequestGroup (or no card) asks the health worker nothing.yes → Accept or decline the guidance
no → Nothing to act on
Any action accepted?
Gateway_Accepted
Read from the decisions: at least one action accepted or modified.yes → Update the care plan
no → Guidance declined

folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.

deployed dev