{"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_topology","feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","contains":"claims, sources, anecdotes, question_graph slice","slug":"radiology-incidental-findings-followup","urls":{"read":"https://miscsubjects.com/api/articles/radiology-incidental-findings-followup/topology"},"how_to_use":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/radiology-incidental-findings-followup/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/radiology-incidental-findings-followup/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"graph_topology","name":"Cross-article graph","what":"Merged claims/sources across condition+stack slugs for one question.","urls":{"read":"https://miscsubjects.com/api/articles/radiology-incidental-findings-followup/graph-topology?question=..."}},{"id":"question_graph","name":"Question graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output).","urls":{"read":"https://miscsubjects.com/api/articles/radiology-incidental-findings-followup/question-graph","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/radiology-incidental-findings-followup/voxels","write":"https://miscsubjects.com/api/protocol/claim"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","why":"Every feature is auditable collective intelligence","how":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/radiology-incidental-findings-followup/topology"},"imessage":null,"router":null,"related":[{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"graph_topology","what":"Merged claims/sources across condition+stack slugs for one question."},{"id":"question_graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output)."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."}],"not_medical_advice":true},"slug":"radiology-incidental-findings-followup","title":"The follow-up was recommended and never happened. The record that proves what was absent, at the moment it mattered.","register":"technical","tags":["governance","radiology","patient-safety","adjudication","use-case"],"updated_at":"2026-07-30T17:56:18.406Z","body_excerpt":"## The finding that was reported and then lost\n\nThe radiologist did the job. The incidental pulmonary nodule was seen, described, and given a follow-up recommendation in the report — a repeat CT at a stated interval. The report was signed, transmitted, and filed. Then nothing happened. No follow-up study was ordered, or it was ordered and never performed, or performed and never compared. The patient returns years later with the finding grown past the point where the recommendation would have mattered.\n\nThis is the closed-loop communication failure, and it is not exotic. The American College of Radiology's Actionable Reporting Work Group exists because the transmission of a finding is not the completion of one: its categories of actionable findings, and the communication obligations attached to each, were written against documented failures of exactly this loop. The patient-safety literature on incidental findings — pulmonary nodules, adrenal masses, thyroid nodules, renal lesions — records, at documented rates that vary by finding type and institution, that a material fraction of recommended follow-ups are never completed. Radiology quality teams do not dispute this; they staff programs against it.\n\nWhen one of these cases surfaces — a malpractice complaint, a peer-review referral, a root-cause analysis — the operative question is narrow and brutal: **at each moment a downstream decision was made, what did the record actually contain?** Did the ordering physician's view include the recommendation? Was the follow-up report in the file when the next encounter was documented? Who relied on a chart that was silent, and can that silence be proven rather than asserted?\n\nEvery system in the current stack answers that question retrospectively. The EHR audit trail shows access events, not what a decision expected to find. The results-management platform shows task states. The deposition reconstructs, from fragments, what someone must have seen. Retrospective reconstruction is precisely the evidence class that fails under adversarial examination — and it fails the quality team as much as the defense, because a program that cannot prove where its loop breaks cannot fix it.\n\n## What tracking systems record, and what they cannot prove\n\nClosed-loop results-management systems — the category several vendors now sell into radiology quality — track recommendations forward: extract the recommendation, create a task, escalate when the window lapses. This is necessary work and this article takes nothing from it.\n\nBut tracking presence is a different evidence class from proving absence. A tracking system records that a task existed and what state it reached. It does not — cannot, by design — produce a record that says: *on this date, a determination was made against this patient's file, and the determination itself declared, contemporaneously and in machine-readable form, that the follow-up report the policy required was expected and not present.* The first is workflow telemetry. The second is evidence of reliance on an incomplete record, created at the moment of reliance, by machinery with no retrospective access to change it.\n\nNo system in the results-management category produces the second artifact. This page describes an instrument that does, states exactly what it is, and states exactly what it is not.\n\n## The absence declaration, mechanically\n\nThe instrument is the same governed decision machinery documented across this site, pointed at a follow-up policy. One determination works like this. The **rule set** — the institution's follow-up policy for the finding class, written criteria: what study, what interval, what counts as completion — is pinned to a content hash, so the version in force is beyond dispute. The **record** under review — the report set and order set for one patient file, or a synthetic fixture standing in for one — is hashed the same way. Several independent model seats, from different training families, each receive the iden","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[{"id":"c1","text":"Radiology reports routinely recommend follow-up imaging for incidental findings, and published patient-safety literature documents that a material fraction of those recommendations are never completed — the closed-loop communication failure the ACR's Actionable Reporting work exists to address.","tier":"system","section":"The finding that was reported and then lost","interaction_risk":false,"status":"active","source_ids":[],"why_material":"The liability and the patient harm both attach to the gap between recommendation and completion, not to the original read.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c2","text":"When a missed follow-up surfaces — in litigation, peer review, or root-cause analysis — the question is what the record showed at the moment each downstream decision was made, and that record is reconstructed after the fact from systems that were never designed to prove absence.","tier":"system","section":"The finding that was reported and then lost","interaction_risk":false,"status":"active","source_ids":[],"why_material":"Retrospective reconstruction is exactly the evidence class that fails under adversarial examination.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c3","text":"Results-management and closed-loop tracking systems record what happened; none of them produce a contemporaneous, per-decision record of what was expected and absent when a determination relied on the record.","tier":"system","section":"What tracking systems cannot prove","interaction_risk":false,"status":"active","source_ids":[],"why_material":"Presence-tracking and absence-proof are different evidence classes; the second is the one missing.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c4","text":"The governing constitution compels every determination to declare the records a competent reviewer would have expected and did not receive — the absence declaration — and the genuine APPROVE on record carries those declarations, sealed only when independent seats derived identically.","tier":"system","section":"The absence declaration","interaction_risk":false,"status":"active","source_ids":["s1","s6"],"why_material":"A compelled, machine-produced statement of absence at decision time is the missed-follow-up instrument itself.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c5","text":"A unanimous verdict is refused when the derivations diverge, so agreement that hides disagreement cannot seal — the discipline that makes an absence declaration trustworthy rather than boilerplate.","tier":"system","section":"The absence declaration","interaction_risk":false,"status":"active","source_ids":["s1","s4"],"why_material":"An absence declaration is only evidence if the machinery producing it refuses false consensus.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c6","text":"The medical precedent already exists on the record: a synthetic prior-authorization fixture adjudicated as an administrative determination against written criteria, with the boundary stated — the models judge whether a record satisfies criteria, never what care is appropriate.","tier":"system","section":"The determination, bounded","interaction_risk":false,"status":"active","source_ids":["s2"],"why_material":"The follow-up question has the same shape: does the file contain the completed follow-up the policy requires, yes or no.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c7","text":"When the file cannot support a conclusion, abstention is itself a sealed outcome: the first clean NO_ACTION seal shows three seats refusing for identical stated reasons, declared absences included.","tier":"system","section":"When the record is silent","interaction_risk":false,"status":"active","source_ids":["s3","s5"],"why_material":"For missed follow-up, the abstention path is the payload: 'cannot conclude — the follow-up report is absent' is the record that matters.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c8","text":"In the 30-case oracle-labelled calibration study — three seats across two model families on synthetic determinate fixtures — glm-5.2 scored 30/30, kimi 29/30 on valid findings, and the gate authorised zero wrong answers in 30 cases.","tier":"system","section":"Calibration, stated with its limits","interaction_risk":false,"status":"active","source_ids":["s7"],"why_material":"The one measured accuracy table that exists, quoted with its scope rather than extrapolated.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c9","text":"The same machinery audits the follow-up policy itself before it governs anything: a governed critique of a case file found eight defects, the lead one in the rule set, not the models.","tier":"system","section":"The policy audit","interaction_risk":false,"status":"active","source_ids":["s8"],"why_material":"Ambiguous follow-up policies produce ambiguous accountability; the input audit catches that with a receipt.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c10","text":"This is not a medical device, has no clinical validation, does not detect findings, and offers no clinical advice; every published run uses synthetic fixtures, and the instrument's only product is a governed record of what was present, what was absent, and what the panel concluded.","tier":"system","section":"What this is not","interaction_risk":false,"status":"active","source_ids":[],"why_material":"A patient-safety audience must not be sold one inch past the evidence, and this names the boundary exactly.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false}],"sources":[{"id":"s1","type":"live_surface","url":"https://miscsubjects.com/a/auditable-reasoning-hardened","title":"The derivation-agreement gate — reasoning compared step by step, not verdicts","summary":"Independent models under a pinned rule set; the gate refuses to authorise when their clause-by-clause derivations diverge, even on a unanimous verdict. Includes the false-convergence defect and its fix.","claim_ids":["c4","c5"],"hash":"a9e212029da38a5cf47ed95ae34264b64eed992cd5f9200ddf14709845126a0e"},{"id":"s2","type":"live_surface","url":"https://miscsubjects.com/a/adjudication-medical-prior-auth","title":"A medical prior-authorization record adjudicated under the constitution","summary":"A synthetic, labeled prior-auth fixture: does the submitted record satisfy written criteria. The determination is administrative, never clinical — the boundary this article inherits.","claim_ids":["c6"],"hash":"04eb50fce056ce4513c5a72e8b7518bb49e936fff866787e2028fa8f5fff61fb"},{"id":"s3","type":"live_surface","url":"https://miscsubjects.com/a/adjudication-abstention-no-action","title":"Abstention as a sealed outcome — cannot-conclude, made machine-comparable","summary":"Making refusal-to-decide a first-class sealed outcome, including the specification defect and the four amendments that ended in the first clean NO_ACTION seal.","claim_ids":["c7"],"hash":"c7eed0fd49dc67ead44ecbac1f8f970451e82139cf19d281389713376fd20ed0"},{"id":"s4","type":"live_surface","url":"https://miscsubjects.com/receipt/inv_o6s0exhodd","title":"A unanimous verdict, refused on divergent derivation","summary":"Three models returned the same verdict citing the same clauses; two derived it differently, so the gate escalated instead of concluding.","claim_ids":["c5"],"hash":"cc230ef4544bc7257ec8287cf80a608fbcfb090353fe94f308f362755d1f210a"},{"id":"s5","type":"live_surface","url":"https://miscsubjects.com/receipt/inv_7rqy8ywuls","title":"The first clean NO_ACTION seal","summary":"Three seats abstaining for identical stated reasons — the same clauses, trigger states, and declared absences — sealed as a permanent, keyless record.","claim_ids":["c7"],"hash":"ffe103f61aa480ebb205a2ed6cfd3a873a9d4cd783c005f5866685b18a176e8e"},{"id":"s6","type":"live_surface","url":"https://miscsubjects.com/receipt/inv_wl0rnh136b","title":"The genuine APPROVE — unanimous verdict, identical derivation","summary":"The clean authorisation on record: every seat fired the same clauses in the same trigger states on the same evidence, absence declarations included.","claim_ids":["c4"],"hash":"01c32c0ae66b94b4febec1d1c709338d3bcd3c44fdeb152396b6e16ae35e32df"},{"id":"s7","type":"live_surface","url":"https://miscsubjects.com/a/adjudication-calibration-study","title":"The calibration study — 30 oracle-labelled cases through the production gate","summary":"Seat accuracy and gate calibration on 30 hashed synthetic determinate fixtures: glm-5.2 30/30, kimi 29/30 on valid findings, and zero wrongful authorisations in 30 cases.","claim_ids":["c8"],"hash":"6451b6dff6f20d8c5b6dca3b5dbb2015ab5bf0a994969bbbeb86b3dd51efa5ee"},{"id":"s8","type":"live_surface","url":"https://miscsubjects.com/receipt/inv_qh3ge2x74b","title":"The instrument auditing its own input: eight defects found","summary":"A governed model asked to critique the case file found the rule set itself defective — the divergence was the input, not the models. The same audit applies to a follow-up policy before it governs anything.","claim_ids":["c9"],"hash":"f215cc78c2875d08a2351c416f1801b72f5fd2e0d7d4c7900fc520f0e01f23e3"},{"id":"em_es_48950eb6c52e4eb8b4b3","type":"email","url":"https://miscsubjects.com/letter-center-for-evidence-based-imaging-2026-07-30","title":"Letter to Dr. Ramin Khorasani — 2026-07-30","claim_ids":[],"hash":"5ef0200043555634ea1f7d36becc2ee3e12879e237adeaa5770072a1134f9b3f"},{"id":"x_2082840412084216101","type":"x","url":"https://x.com/CannibalCapital/status/2082840412084216101","title":"X post announcing radiology-incidental-findings-followup — 2082840412084216101","quote":"Radiology follow-up: the compelled absence declaration as the missed-follow-up instrument — a contemporaneous sealed record that the follow-up report was absent when a determination relied on it.","claim_ids":[],"hash":"7ed473e2ffe9e1adc0120dc2c70851d7c511d8aef13e5ec792a78665bfc5891b"}],"anecdotal_sources":[{"id":"x_2082840412084216101","type":"x","url":"https://x.com/CannibalCapital/status/2082840412084216101","title":"X post announcing radiology-incidental-findings-followup — 2082840412084216101","quote":"Radiology follow-up: the compelled absence declaration as the missed-follow-up instrument — a contemporaneous sealed record that the follow-up report was absent when a determination relied on it.","claim_ids":[],"hash":"7ed473e2ffe9e1adc0120dc2c70851d7c511d8aef13e5ec792a78665bfc5891b"}],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"radiology-incidental-findings-followup","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":10,"retracted_claims":0,"cut_claims":0,"challenges":0,"scrub_events":0,"note":"Retracted/cut claims stay on ledger but are excluded from ask unless ?include_inactive=1"},"counts":{"claims":10,"claims_total":10,"sources":10,"anecdotal":1,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}