Generated from folio-assistant-core/collab/processes/content/guideline-updates.bpmn by gen-processes-viz.ts — do not edit here. All processes · folio-assistant-core processes

Guideline Updates

Process_GuidelineUpdates · strict · 8 step(s)

Taking up a new version of a guideline, or a changed lower layer, is a re-pin and a review at once. The steward maps the affected layers and re-pins them in dependency order. For each re-pin, the adaptation team compares the old version, the new version and its own adaptations. A change that touches no adaptation or policy merges on the technical path. One that does goes to the adaptation committee, which decides for each adaptation whether to keep, revise or retire it. Revisions are ordinary content changes (Process_ContentChangeReview), and the re-pin merges with them. The loop runs until every layer is current.

BPMN diagram: Guideline Updates

How it connects

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

Lanes — who acts

lanerolewhat it does here
Guideline publisherpublication-managerThe body that issues the guideline (for example WHO). It publishes a new version with change notes that say what changed and why. It does not decide how a country adapts. That is the adaptation committee’s call.
Re-pin steward and build pipelinemerge-stewardMoves the pins, one layer at a time and in dependency order, so each site re-pins only after every layer it takes from has landed. Each re-pin is a pull request with a staging preview and the impact report attached. In rapid development this lane runs on its own for changes that touch no adaptation.
Adaptation team (human or agentic)business-analystThe country or implementer team that keeps the adaptations: the local content, overlays and overrides that sit on top of the guideline. It reads the impact report, says which adaptations and policies a change touches, and makes the revisions the committee decides.
Adaptation committee (policy, clinical, programme)authoring-committeeThe stakeholders who own the adapted guideline: policy, clinical and programme leads, and others the country names. They review the impact with the old and new versions side by side and decide, for each adaptation, whether to keep, revise or retire it. Their decisions are recorded, and they are what the release notes cite.

Steps

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

steplaneskill / sub-processwhat it does
Publish the version with its change notes
Task_ChangeNotes
Guideline publishercontent-publishThe publisher states what changed, what was added and what was withdrawn, and why, in words a country team can act on. The notes go with the release, so the comparison below starts from the publisher’s own account rather than only from a diff.
Map the affected layers in order
Task_MapCone
Re-pin steward and build pipelineremote-mountRun the re-pin planner (mount:repin:cone) with the fleet and the changed repository. It lists every site downstream in waves, so a site moves only after the layers it takes from have moved, and marks which sites are ready now.
Open the re-pin for the next ready layer
Task_OpenRepin
Re-pin steward and build pipelineremote-mountFor each site that is ready now, open one re-pin pull request that moves its pins from the old version to the new one. Its staging preview is a full build with QA. A site’s standing consent may let its own workflow open this pull request.
Compare old, new and our adaptations
Task_Impact
Adaptation team (human or agentic)rendered-impactAttach the impact report to the re-pin: the changes that reach this site (only what it mounts), and its own files that look like adaptations of a changed file. The team adds what a diff cannot see: which policies, local decisions and translations rest on the changed text.
Review the impact with stakeholders
Task_Review
Adaptation committee (policy, clinical, programme)content-reviewThe committee reads the old version, the new version and each affected adaptation side by side on the staging preview, and hears the adaptation team’s account of what rests on them.
Decide each adaptation: keep, revise or retire
Task_Decide
Adaptation committee (policy, clinical, programme)decision-auditOne recorded decision per affected adaptation, with its reason: keep it as is, revise it to the new version, or retire it because the new version now covers it. A decision to diverge from the new version is recorded as such.
Revise the adaptations as decided
Task_Revise
Adaptation team (human or agentic)calls Content Change and Review
content-review
Each revision is an ordinary content change, reviewed on its staging preview through content change review, on the re-pin’s branch or a branch that merges with it.
Merge the re-pin with its decided revisions
Task_Merge
Re-pin steward and build pipelineprepare-mergeThe re-pin merges when its checks are green and every decision it needs is recorded. Its pull request cites the decisions, which become the release notes for this site’s update.

Decisions

3 of 3 decision(s) carry no documentation — gateway-documented lists them.

decisionwhat decides itbranches
Does the change touch an adaptation or policy?
Gw_Touches
—yes → Review the impact with stakeholders
no → Merge the re-pin with its decided revisions
Any adaptation to revise?
Gw_Revise
—yes → Revise the adaptations as decided
no → Merge the re-pin with its decided revisions
More layers left to re-pin?
Gw_More
—yes → Open the re-pin for the next ready layer
no → Every layer current with the new version

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