Generated from smart-base/L1/processes/classify-and-code-content.bpmn by gen-processes-viz.ts — do not edit here. All processes · smart-base processes

Classify and code content

Process_ClassifyAndCodeContent · advisory · 5 step(s)

Classifies and codes L1 extracted statements (recommendations, implementation practices, remarks, proposed coverage exclusions) and L2 DAK slots (personas, business processes, guideline domains, conditions, interventions, medicines, GRADE ratings), following the terminology-coding methodology and the classify-and-code-content skill. The authoring agent runs terminology-lookup down the four-rung reuse-first ladder, records provenance (declared, context, inferred) and candidate status, and stages the result. A person in the l1-extraction-reviewer lane signs or rejects each exclusion proposed in exclusions.proposed.json against the printed page (sections/page-NNN.md). A person in the terminologist / ontologist lane then adjudicates the candidate codings, SKOS match precision (exactMatch vs closeMatch) and any Rung 4 local glossary candidates.

BPMN diagram: Classify and code content

How it connects

  • Called by: no call activity names this process
  • Calls: none
  • Presented on: no docs page section shows this diagram
  • Skill: classify-and-code-content
  • Running instances: none recorded

Lanes — who acts

lanerolewhat it does here
Authoring agentauthoring-agentIdentifies classifiable slots and normative sentences, runs terminology-lookup down the reuse-first ladder, records link provenance and candidate status, and stages codings and proposed exclusions for human review. Never signs an exclusion or approves its own candidate term.
L1 extraction reviewer (person)l1-extraction-reviewerA person in the l1-extraction-reviewer role. Reads each sentence proposed for exclusion in its printed-page context and signs the exclusion (signedOffBy) or rejects it, so no normative guidance is silently dropped.
Terminologist / ontologist reviewer (person)terminologistA person in the terminologist role, equipped with ontologist, glossary-terms, terminology-management and classify-and-code-content. Reviews the staged classifications and codings and records the verdict.

Steps

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

steplaneskill / sub-processwhat it does
Identify slots and proposed exclusions
Task_IdentifySlots
Authoring agentclassify-and-code-content
recommendation-extraction
Enumerate the classifiable slots in the L1 statements or L2 component (condition, intervention, persona, medicine, domain, business-process, recommendation-strength, recommendation-direction, evidence-certainty) and any proposed L1 coverage exclusions in exclusions.proposed.json naming l1-extraction-reviewer as signerRole.
Run reuse-first lookup and record candidates
Task_LookupAndCode
Authoring agentclassify-and-code-content
recommendation-scenarios
glossary-terms
Run the terminology-lookup Tool down the four reuse-first rungs of the terminology-coding methodology: (1) target guide vocabulary, (2) smart-base generic personas, GRADE code lists and guideline-domain glossary, (3) external WHO-FIC/ILO standards (ICD-11, ICHI/CDHIv2, ISCO-08, ATC), (4) local glossary candidate (status: candidate, source: extracted), or could-not-determine for business-process with its WARNING line.
Stage codings, warnings and exclusions for review
Task_StageForReview
Authoring agentstaging-review
interaction-modality
Write the candidate codings, provenance bases, warnings report and any unsigned exclusions.proposed.json entries, and request review with deep links to the staged pages and the printed page sections.
Check exclusions against page and sign
Task_ReviewExclusions
L1 extraction reviewer (person)classify-and-code-content
recommendation-extraction
content-review
Open library/<doc_id>/sections/page-NNN.md beside exclusions.proposed.json. Read each candidate sentence on the printed page, check that the proposed reason (background-fact, manufacturer-statement, editorial, research-question, duplicate-of) holds without dropping normative guidance, and sign the exclusion (signedOffBy) or reject it with a reason.
Adjudicate slot codings and glossary candidates
Task_ReviewCodings
Terminologist / ontologist reviewer (person)classify-and-code-content
ontologist
glossary-terms
terminology-management
content-review
Review each slot’s classification and code against the terminology-coding methodology: the authoritative scheme for the slot, the reuse-first rung, skos:exactMatch vs skos:closeMatch precision (ontologist), and any Rung 4 glossary candidates (promote valid ones from candidate to authored per glossary-terms, or replace them with an existing code).

Decisions

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

decisionwhat decides itbranches
Proposed exclusions?
Gateway_HasExclusions
Unsigned entries in exclusions.proposed.json go to the l1-extraction-reviewer first, so exclusions are verified against the printed page before coding sign-off; otherwise straight to terminologist/ontologist review.yes → Check exclusions against page and sign
no → Adjudicate slot codings and glossary candidates
Exclusions signed?
Gateway_ExclusionVerdict
All signed: on to terminologist/ontologist review. Any rejected as normative: back to the authoring agent to re-curate the sentence as an L1 node.reject-exclusion → Gateway_Rework
signed → Adjudicate slot codings and glossary candidates
Coding verdict?
Gateway_TerminologistVerdict
approve marks candidate links reviewed and promotes approved glossary candidates to authored; request-changes returns the mappings or glossary candidates to the authoring agent with findings.request-changes → Gateway_Rework
approve → Content classified, coded and signed off

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