Generated from smart-base/L2/collab/processes/dth-authoring.bpmn by gen-processes-viz.ts — do not edit here. All processes · smart-base processes

DTH authoring

Process_DthAuthoring · advisory · 37 step(s)

Produces a WHO Digital Transformation Handbook (DTH) from its sources to publication, in seven stages that each end in a recorded milestone: initiate (M0 charter), ingest sources into the library (M1 library frozen), outline and scope (M2 outline agreed), structured drafting (M3 zero draft), working-group feedback (M4), public comment (M5 released, M6 dispositioned), and finalise and publish (M7). Milestones are recorded checkpoints, not gates: each is written as a note on the handbook’s epic bean (which milestone, when, evidence), so the site can show stage and progress. Review runs beside drafting as QA, as in smart-guideline-end-to-end.bpmn. Structured drafting uses the smart-base DAK block kinds for personas, scenarios, processes, decisions, data elements, indicators and requirements, and each track calls Process_L2ComponentEditReview, as l2-dak-authoring.bpmn does. Contributor feedback from the contributor log sheet and from GitHub pc: comments lands in one review store. Handbooks ingested from a published WHO PDF (PHC, SC, PC, SFP) enter at stage 1 with their library built and their outline given by the publication; dth-hrh, authored natively, is the pilot. Steps with no platform subprocess are marked as placeholders in their documentation. Empirical content (figures, statistics, country examples) stays as cited narrative blocks and never enters formal content.

BPMN diagram: DTH authoring

How it connects

Lanes — who acts

lanerolewhat it does here
DTH lead (programme manager)programme-managerOwns the handbook. Sets its scope and its place in the DIIG once, forms the technical working group (TWG), and records the roles and RACI that every later lane is scoped against.
Work plan (beans)work-planSeeded once from the scope, with one bean per stage and per structured-drafting track, so progress is visible without reading the diagram.
LibrarianlibrarianBrings every source into the handbook’s library/ as received and frozen: WHO publications through who-iris, TWG outlines and workbooks as uploads. Never edits a source to answer a comment.
Business analystbusiness-analystDrafts the outline and the structured content. Every structured track uses a smart-base DAK block kind and calls the shared edit-and-review subprocess.
TerminologistterminologistBuilds the glossary as a SKOS scheme from the TWG’s candidate definitions and links each term to the smart-ra concept it matches or narrows. Never chooses between conflicting definitions; records them as alternatives.
Architect group and handbook ownersreviewerReview the structured content beside drafting, as QA and not as a gate: the architect group for ArchiMate links and new kinds, the owners of each handbook for content shared with theirs.
TWG and contributorsfeedback-providerComment through the contributor log sheet or on GitHub (a pc: line in any issue or PR conversation). Both channels land in one review store.
EditoreditorImports comments into the review store, groups them into change sets, decides dispositions, and runs editorial and voice QA.
Publication managerpublication-managerPublishes the final handbook and, when permitted, hands it to the WHO repository.

Steps

2 of 37 step(s) carry no documentation — activity-documented lists them.

steplaneskill / sub-processwhat it does
0 · Scope the DTH and place it in the DIIG
Task_Scope
DTH lead (programme manager)content-planName the health-system area, the audience and the DIIG phase the handbook supports, citing the one DIIG phase figure (DIIG section 1.1, Figure 1.1.1). Decide which DTHs and which smart-ra content it builds on.
Form the TWG; record roles and RACI
Task_Team
DTH lead (programme manager)content-planRecord who is involved and in which role. Roles are named by id, never free text, so they can bind BPMN lanes later. There is no RACI kind; the RACI is a table block.
Create the DTH repository from the DTH layout
Task_Scaffold
Business analystdocument-structureRun bun run smart-base/scripts/dth-init.ts with –pins-from an existing DTH’s index.config.json. It writes the instance declaration (folio, glossary, uploads, beans and todos branches), index.config.json (mounting who-iris, smart-base, the platform layers and smart-ra), package.json scripts for the shared checks, the review sheet sync (–sheet) and the files from templates/dth/ (AGENTS.md, session-start hook, PR checks workflow).
Seed the work plan
Task_SeedBeans
Work plan (beans)todo-managerOne bean per stage and per drafting track, children of the handbook’s epic.
Record milestone M0 · Charter recorded
M0
Work plan (beans)todo-managerMilestone: repository, declaration, TWG, roles and RACI exist. Recorded, not enforced.
1 · Ingest sources into library/
Task_Ingest
Librarianlibrary-ingestionEvery source as received, frozen: WHO publications through who-iris, the TWG outline and workbooks from uploads/.
Extract L1 from WHO publications
Task_L1
Librarianl1-document-ingestionSections, figures, tables and the L1 knowledge graph for each WHO publication the handbook draws on.
Account for every normative sentence
Task_Coverage
Librarianl1-coverageEach normative sentence is captured or excluded; exclusions are signed by a person, never by the agent that proposed them.
Publish extracted statements
Call_PublishStatements
Business analystcalls Publish extracted statements with source links
publish-extracted-statements
Statements extracted from the L1 sources (recommendations, requirements, scenario candidates) are published as pages of the handbook and in the shared l1-extraction viewer, each linked to its library entry and section, once coverage has accounted for every normative sentence and before the library is frozen. The sub-process is core’s, the same for every content type; smart-base supplies the collector (l1-statement-lists) and the handbook only the page look.
Record milestone M1 · Library frozen
M1
Librariantodo-managerMilestone: every source in library/, coverage accounted. Recorded, not enforced.
2 · Outline chapters against the dth kind
Task_Outline
Business analystdocument-structureMap the outline onto the dth document kind’s sections and report every required section that is missing. dth-hrh’s build_from_outline.py is the only instance; there is no general outline seed. Placeholder: no platform subprocess; done by hand, as for dth-hrh.
Draft introduction, audience and DIIG alignment
Task_Intro
Business analystdocument-authoringThe three required opening sections of the dth kind: audience and how to use, DIIG and SMART alignment, health programme context.
Build glossary candidates from the TWG workbook
Task_GlossaryCandidates
Terminologistterminology-managementOne SKOS candidate per (concept, source); only a person moves a term to authored.
List processes, roles, decisions and indicators to model
Task_Inventory
Business analystcontent-planThe inventory that seeds the structured-drafting tracks: each business process becomes BPMN, each role a structured block, each stated decision rule a DMN table.
TWG reviews the outline
Task_OutlineReview
TWG and contributorscontent-feedbackFirst contributor-feedback round, through the contributor log sheet and GitHub.
Record milestone M2 · Outline agreed
M2
TWG and contributorstodo-managerMilestone: the outline’s round-1 comments are dispositioned. Recorded, not enforced.
Personas and roles
Call_Personas
Business analystcalls L2 component edit and review
l2-dak-authoring
l2-component-edit-review
Persona and actor-definition blocks; organisational roles and governance bodies get their own kind once it exists. Calls Process_L2ComponentEditReview.
User scenarios
Call_Scenarios
Business analystcalls L2 component edit and review
l2-dak-authoring
l2-component-edit-review
User-scenario blocks naming their personas by id. Calls Process_L2ComponentEditReview.
Business processes · BPMN
Call_Bpmn
Business analystcalls L2 component edit and review
bpmn-authoring
l2-component-edit-review
One BPMN per business process; every lane bound to a persona or role id. Calls Process_L2ComponentEditReview.
Decision tables · DMN
Call_Dmn
Business analystcalls L2 component edit and review
dmn-authoring
l2-component-edit-review
Only rules the text states. A decision the text names without a rule is recorded as a decision point, not filled in. Calls Process_L2ComponentEditReview.
Data elements, indicators, requirements
Call_Data
Business analystcalls L2 component edit and review
l2-dak-authoring
indicator-extraction
l2-component-edit-review
data-element, indicator, functional and non-functional requirement blocks, with their fields as data rather than Markdown tables. Calls Process_L2ComponentEditReview.
Planning steps per chapter
Call_Steps
Business analystcalls L2 component edit and review
document-authoring
l2-component-edit-review
Each chapter’s inputs, steps, resources, outputs, risks and mitigations as the shared step table. Calls Process_L2ComponentEditReview.
Link to smart-ra ArchiMate
Call_Archimate
Business analystcalls L2 component edit and review
archimate-models
l2-component-edit-review
Every block that names an architecture element links to its smart-ra element or view; new elements go to smart-ra, not the handbook. Placeholder: no platform subprocess; done by hand, as for dth-hrh. Calls Process_L2ComponentEditReview.
Link glossary to smart-ra SKOS
Call_Glossary
Business analystcalls L2 component edit and review
terminology-management
l2-component-edit-review
Each handbook term is exactMatch, closeMatch or narrower to a smart-ra concept; conflicts are raised as issues on smart-ra. Calls Process_L2ComponentEditReview.
Validate the draft
Task_Validate
Business analystcontent-validateEvery structured block validates against its kind; required dth sections present; no unlinked architecture names; no empirical claims in formal content.
Architect group and handbook owners review
Task_ArchReview
Architect group and handbook ownerscontent-reviewRuns beside validation, as QA. New kinds and shared schemas are reviewed here before they are built.
Record milestone M3 · Zero draft
M3
Business analysttodo-managerMilestone: every required section drafted and every structured block validates. Recorded, not enforced.
4 · Comment via contributor log sheet or GitHub pc:
Task_Comments
TWG and contributorscontent-feedbackThe contributor log (Google Sheet) and pc: lines on GitHub issues and PRs.
Import into review/wg-comment and form change sets
Task_Import
Editorpublic-commentpublic-comment import –store review/wg-comment; change sets group comments that change the same text.
Record milestone M4 · Working-group draft
M4
Editortodo-managerMilestone: all working-group comments dispositioned. Recorded, not enforced.
5 · Open public comment
Task_OpenPublic
Editorpublic-commentA separate store, review/public-comment, and the public-comment review sheet.
Record milestone M5 · Public draft released
M5
Editortodo-managerMilestone: the public draft is out for comment.
Public comments
Task_PublicComments
TWG and contributorscontent-feedback—
Disposition comments and apply change sets
Task_Disposition
Editorpublic-commentChanges to structured content go back through its kind’s edit-and-review subprocess.
Record milestone M6 · Comments dispositioned
M6
Editortodo-managerMilestone: every public comment dispositioned.
6 · Editorial, voice and translation QA
Task_Qa
Editorquality-controlThe DTH voice (smart-base skills/voices/who-digital-transformation-handbook), figures and translations.
Publish the handbook
Task_Publish
Publication managerdocument-publishing—

Decisions

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

decisionwhat decides itbranches
All working-group comments dispositioned?
GW_WgDone
—yes → Record milestone M4 · Working-group draft
no: revise → GW_DraftMerge

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