Generated from
smart-base/L1/skills/smart-l1/classify-and-code-content.md— do not edit here.
classify-and-code-content
Skill id:
classify-and-code-content· Package:authoring-who-smart-guidelines· Methodology:terminology-coding· Process:classify-and-code-content.bpmn(Process_ClassifyAndCodeContent) · Tool:terminology-lookup
An agent proposes classifications, codes and coverage exclusions; a person in the named reviewer lane judges and signs them. The process has three lanes:
authoring-agentcodes slots and stages candidates (Step 1).l1-extraction-reviewer(a person) signs or rejects proposed L1 exclusions against the printed page (Step 2).terminologist(a person, the terminologist / ontologist reviewer) judges candidate codings, SKOS mapping predicates and glossary candidates (Step 3).
Input and output
- Input contract:
input.schema.json - Output contract:
output.schema.json
Step 1 — Agent: classify and code slots with terminology-lookup
For each slot in an L1 extraction or L2 component, run the Tool, record
provenance (declared, context, inferred) and status: "candidate", and
stage the codings and any proposed exclusions for review:
bun run smart-base/scripts/terminology-lookup.ts \
--slot <condition|intervention|persona|medicine|domain|business-process|recommendation-strength|recommendation-direction|evidence-certainty> \
--query <term-or-code> \
[--vocabulary <guide-vocabulary.json>] \
[--generic <smart-base-generic-personas.json>] \
[--scheme <scheme-id>] \
[--out <result.json>]
Stop at the first rung that matches
(terminology-coding §2):
- Rung 1 (
rung-1-target-guide): the target guide’s own persona or business process froml1-scenario-vocabulary/v1, when its scope covers the statement. - Rung 2 (
rung-2-smart-base):smart-basegeneric personas (DAK.Persona.*), GRADEcode-lists/*.json, or theguideline-domainSKOS scheme (clinical,public-health,health-system-strengthening). - Rung 3 (
rung-3-external-standard): the slot’s external standard (ICD-11,ICHI/CDHIv2,ISCO-08,ATC), distinguishingskos:exactMatchfromskos:closeMatchperontologist. - Rung 4 (
rung-4-local-candidate):- Unmatched persona or domain concept: record a local glossary
candidate (
status: "candidate",source: "extracted") perglossary-termsand emitWARNING <slot>-glossary-candidate. - Unmatched business process: never invent a process; record
could-not-determineand emitWARNING process-not-determined.
- Unmatched persona or domain concept: record a local glossary
candidate (
Step 2 — l1-extraction-reviewer: read proposed exclusions against the page and sign
When recommendation-candidates writes
exclusions.proposed.json, every entry carries:
{
"signerRole": { "role": "l1-extraction-reviewer" }
}
and no signedOffBy. Until a reviewer signs it, l1-coverage counts the
sentence as unaccounted and coverage stays below 100 %. In
Lane_ExtractionReviewer:
- Open the printed page beside the work list. Locate
location(p<page>:s<n>) inlibrary/<doc_id>/sections/page-<NNN>.md(and the rendered page image when layout is ambiguous). - Read the sentence in place, with its paragraph, heading and table context — never judge an exclusion from the isolated sentence.
- Check the proposed
reasonagainst the five closed reasons:background-fact— epidemiology, disease burden, history, or biological fact with no normative action for a guideline user;manufacturer-statement— a product insert or manufacturer specification quoted as context rather than a WHO recommendation;editorial— licence text, imprint, how-to-read-this-document prose, chapter navigation checkpoints, or glossary definitions;research-question— a gap or priority for future research, not a current practice or recommendation;duplicate-of:<id>— a verbatim or near-verbatim repetition of a statement already captured under<id>, verified against<id>’s statement text.
- Sign or reject:
- Sign if the sentence is non-normative for the stated reason: record
signedOffBy(the reviewer’s handle) and timestamp in the curation / exclusions file, and re-runl1-recommendation-candidatesso coverage updates. - Reject if it states a recommendation, implementation practice or
remark that belongs in L1, with a reason, so the
authoring-agentre-curates the location as a node.
- Sign if the sentence is non-normative for the stated reason: record
Step 3 — terminologist: review candidate codings and glossary candidates
In Lane_Terminologist, the terminologist (equipped with
ontologist,
glossary-terms,
and terminology-management)
judges each staged coding:
- Scheme and rung: the slot was coded against the scheme named in
terminology-coding§1, and no higher rung held an applicable concept. - Precision: no narrower or broader concept is asserted as
exactMatch(usecloseMatch). - Glossary candidates: for each Rung 4 candidate, promote it to
status: "authored"(checking definition quality andskos:broader/skos:closeMatchlinks), replace it with an existing code from Rungs 1–3, or reject it. - Verdict: record (
approve,request-changes, orreject) in the mapping (review: {by, at}) or componentQaReview.
Input and output contracts
What this skill takes and gives, as a class diagram drawn from its JSON Schema contracts by the schemas viewer’s own renderer. Each box links to its definition; each type to its specification.
- input:
smart-base/L1/schemas/skills/classify-and-code-content/input.schema.json - output:
smart-base/L1/schemas/skills/classify-and-code-content/output.schema.json
Processes that run this skill
This skill has its own process: Classify and code content.
| process | step(s) that name it |
|---|---|
| Classify and code content | Identify slots and proposed exclusions; Run reuse-first lookup and record candidates; Check exclusions against page and sign; Adjudicate slot codings and glossary candidates |