Overview
This ledger records each document whose substance moved from a working repository into this bundle. It is the work list for the follow-up round in which working repositories replace migrated documents with links here. Add a row whenever you migrate, per the authoring guide.
Ledger
| Date | Source repository | Source path | Commit | Destination | Replace source with link? |
|---|---|---|---|---|---|
| 2026-09-21 | ACR-RSNA-CDEs | CONTEXT.md (next-gen-2026) | 44836c19f4e025cf1684a015ed5cc63c29eaf7f3 | knowledge/glossary/data-element.md, finding-class.md, measurement.md, element-binding.md, assessment-scheme.md, anatomic-scope.md | no, upstream working glossary stays with its branch |
| 2026-09-21 | ACR-RSNA-CDEs | notes/oifm-overview.md (next-gen-2026) | 44836c19f4e025cf1684a015ed5cc63c29eaf7f3 | knowledge/glossary/finding-model.md, presence.md, change-from-prior.md, anatomic-scope.md, technical-finding.md | no, itself a copy of findingmodels prompts/overview.md |
| 2026-09-21 | ACR-RSNA-CDEs | notes/ihe-idr-extract.md (next-gen-2026) | 44836c19f4e025cf1684a015ed5cc63c29eaf7f3 | knowledge/glossary/imaging-diagnostic-report.md, fhir-condition.md, cde-labeled-fhir-observation.md | no, extract stays with the CDE work |
| 2026-09-21 | findingmodel | packages/findingmodel/src/findingmodel/finding_model.py | 75afd39a400419dcfaf7c8d4a34f065b4d804e0d | knowledge/glossary/oifm.md, finding-model.md, attribute.md, attribute-value.md, tag.md, measurement.md, oidm-organization-code.md, presence.md | no, code docstrings stay with the code |
| 2026-09-21 | findingmodel | packages/oidm-common/src/oidm_common/models/index_code.py | 75afd39a400419dcfaf7c8d4a34f065b4d804e0d | knowledge/glossary/index-code.md | no, code docstring stays with the code |
| 2026-09-21 | findingmodel | packages/findingmodel/src/findingmodel/contributor.py | 75afd39a400419dcfaf7c8d4a34f065b4d804e0d | knowledge/glossary/contributor.md, oidm-organization-code.md | no |
| 2026-09-21 | findingmodel | packages/anatomic-locations/src/anatomic_locations/models/{location,enums}.py | 75afd39a400419dcfaf7c8d4a34f065b4d804e0d | knowledge/glossary/anatomic-location.md, laterality.md, contained-by-and-part-of.md, body-region.md, fma.md | no |
| 2026-09-21 | findingmodel | docs/canonical-structured-metadata-and-enrichment-rewrite.md (feature/metadata-cleanup) | 1942b06a91d6a5c5eefe10f99a7273e41e24be01 | knowledge/glossary/tag.md, body-region.md, index-code.md | pending, design doc belongs with the branch until it lands |
| 2026-09-21 | findingmodels | schema/finding_model_schema.md | 4475ac1bcb591f1a0951b2082b59208def173a5d | knowledge/glossary/oifm.md, attribute.md, contributor.md | yes, once references/finding-model-schema.md is verified |
| 2026-09-21 | findingmodels | CLAUDE.md | 4475ac1bcb591f1a0951b2082b59208def173a5d | knowledge/glossary/finding-model.md, index-code.md, snomed-ct.md, gamuts.md | no, repository conventions stay with the code |
| 2026-09-21 | findingmodels | lists/README.md (taxonomy-export-2026-08-15) | a30c3c95fa3943e7340ce87575f4b1b926987eb8 | knowledge/glossary/finding-taxonomy.md | yes, once semantic-foundation/finding-models/finding-taxonomies.md exists |
| 2026-09-21 | findingmodels | docs/plans/definition_cleanup.md | 4475ac1bcb591f1a0951b2082b59208def173a5d | knowledge/glossary/gamuts.md, change-from-prior.md | no, open plan stays with the repository |
| 2026-09-21 | imaging-problem-list | README.md (main) | 06f64a7893b444b761dc069ed86140a081195eac | knowledge/glossary/exam-finding-list.md, imaging-problem-list.md, fhir-diagnostic-report.md, fhir-condition.md, provenance.md | yes, once data-structures/ is written |
| 2026-09-21 | imaging-problem-list | CLAUDE.md (main and dev) | 06f64a789… and 36fa30c7383bf687d7bc17815282a93e123a56cb | knowledge/glossary/exam-finding-list.md, imaging-problem-list.md, observation.md, loinc.md, exam-type.md, presence.md | no, agent guidance stays with the code |
| 2026-09-21 | imaging-problem-list | docs/anatomic-location-assignment-rules.md (dev) | 36fa30c7383bf687d7bc17815282a93e123a56cb | knowledge/glossary/laterality.md, body-region.md, anatomic-scope.md, coding.md | yes, full migration owned by the data-structures agent |
| 2026-09-21 | imaging-problem-list | docs/technical-imaging-findings.md (dev) | 36fa30c7383bf687d7bc17815282a93e123a56cb | knowledge/glossary/technical-finding.md | yes, full migration owned by the data-structures agent |
| 2026-09-21 | imaging-problem-list | initial-extraction-plan.md, prompts/validator_prompt_example.md, docs/coding-agent-design.md (dev) | 36fa30c7383bf687d7bc17815282a93e123a56cb | knowledge/glossary/extraction.md, coding.md, presence.md, change-from-prior.md | no, engineering design stays with the code |
| 2026-09-21 | anatomiclocations.org | docs/index.markdown, docs/code.markdown, data/body_parts_schema.json | 1f39fa45f621cef947a3f3ef1f869334cfa5c841 | knowledge/glossary/anatomic-location.md, contained-by-and-part-of.md, radlex-id.md, exam-type.md, radlex.md | yes, once semantic-foundation/anatomic-locations/ is written |
| 2026-09-21 | BodyPartIndex.py | README.md | 388ae0a6da92f5ee4cf36620bbeeabe223938471 | knowledge/glossary/laterality.md | no, library usage stays with the library |
| 2026-09-21 | med-ontology-lookup | README.md, docs/product-roadmap.md | a1fd3ae7ca6a28bb7e5af6838fe4167938084389 | knowledge/glossary/umls.md, loinc.md, loinc-rsna-radiology-playbook.md, snomed-ct.md, fma.md, radlex.md, exam-type.md | pending, roadmap is the only written exam-type design |
| 2026-09-21 | OpenImagingDataModel.py | openimagingdatamodel/observation/observation.py, cde_set/finding_model.py | 455e5b68d730ea8829083d73064de0ec316d3c4a | knowledge/glossary/observation.md, cde-labeled-fhir-observation.md, finding-model.md | no, lineage repository kept as-is |
| 2026-09-21 | OpenImagingDataModel.ts | packages/cde_set/data/guide_to_elements.md | 7c97c33a23323358caa542973dc30d46b618d8a2 | knowledge/glossary/cde-element.md | no, lineage repository kept as-is |
| 2026-09-21 | FHIRSamples | lung_ca_screening_example/*.json | 9ae2fa934298e51789e355c9f4e0b71fabf6b5aa | knowledge/glossary/cde-labeled-fhir-observation.md, cde-set.md, cde-element.md, assessment-scheme.md, provenance.md, fhir-diagnostic-report.md, snomed-ct.md | no, samples stay as lineage evidence |
| 2026-09-21 | common_data_elements | README.md | 35536d8c858bcd33e730a00c919edaef2e310a0b | knowledge/glossary/cde.md, cde-set.md, radelement.md | no, catalog described and linked, never copied |
| 2026-09-21 | openimagingdata.org | schemas/schema_differences.md, README.md | fb431dfc81801a5a8e621c0e8bf2acd20f74be7d | knowledge/glossary/cde-set.md, cde-element.md, index-code.md, oidm.md | yes, gap analysis is still current and belongs here |
| 2026-09-21 | CDEStaging | README.md | b814a102655054ac08b3c118cb1977a387655a8b | knowledge/glossary/cde.md, extraction.md | no |
| 2026-09-21 | IPL-MVP-ExtractionAndLabeling | README.md | b06948fa417aeff0a6a4b97729c915b3ce5d5ed4 | knowledge/glossary/coding.md | no |
| 2026-09-21 | (deck) gamma.app | Open Imaging Data Model 2026 Status Update | live, January 2026 | knowledge/glossary/oidm.md, oifm.md, cde.md, observation.md, exam-finding-list.md, imaging-problem-list.md, imaging-persona.md, imaging-diagnostic-report.md, open-imaging-reporting-sdk.md, provenance.md, extraction.md, assessment-scheme.md | no, external presentation |
| 2026-09-21 | (site) openimagingdata.org | About page and selected posts | live | knowledge/glossary/oidm.md, cde.md, cde-labeled-fhir-observation.md, open-imaging-reporting-sdk.md | no, external site |
| 2026-09-21 | openimagingdata/UseCases | Index.md | 71a90d2ab2efeee4c4303dc0aef27ed3d70a6c99 | /history/use-cases.md | Yes, repository is inactive |
| 2026-09-21 | openimagingdata/UseCases | README.md | 71a90d2ab2efeee4c4303dc0aef27ed3d70a6c99 | /history/use-cases.md | Yes, repository is inactive |
| 2026-09-21 | openimagingdata/CDETemplateDemo | mapper-logic/src/mappers/obsToMustache.ts, mapper-ui/public/sample_templates/RDES44_Pneumothorax/template1.mustache | e09f2553de58b2c88ea26e9673750a62803d4dbc | /history/cde-template-rendering.md | No, code stays with the code |
| 2026-09-21 | openimagingdata/CDEStaging | docs/report_extraction_process.md | b814a102655054ac08b3c118cb1977a387655a8b | /history/extraction-approaches.md | No, summarized only; the worked example stays in the repo |
| 2026-09-21 | openimagingdata/IPL-MVP-ExtractionAndLabeling | README.md | b06948fa417aeff0a6a4b97729c915b3ce5d5ed4 | /history/extraction-approaches.md, /applications/ipl-mvp-extraction.md | No, summarized only |
| 2026-09-21 | openimagingdata/ReportFindingRefiner | README.md | 3efd785aea30c455a3afd120d62da2c6af3d662d | /history/extraction-approaches.md | No, architecture description stays with the code |
| 2026-09-21 | openimagingdata/openimagingdata.org | schemas/schema_differences.md | fb431dfc81801a5a8e621c0e8bf2acd20f74be7d | /history/lineage-repositories.md (summary); full content belongs in /semantic-foundation/common-data-elements/cdes-and-radelement.md | Yes, repository is lineage |
| 2026-09-21 | openimagingdata.org (live site) | 15 posts and the About page | fetched 2026-09-21 | /history/site-articles.md | No, the site stays canonical |
| 2026-09-21 | (deck) gamma.app | Open Imaging Data Model 2026 Status Update | live, January 2026 | knowledge/references/status-update-2026-01.md | no, external presentation |
| 2026-09-21 | openimagingdata/findingmodels | schema/finding_model_schema.md | 4475ac1bcb591f1a0951b2082b59208def173a5d | /references/finding-model-schema.md | Yes. The prose mirror has drifted from the Pydantic definitions and should point here instead. |
| 2026-09-21 | talkasab/anatomiclocations.org | data/body_parts_schema.json | 1f39fa45f621cef947a3f3ef1f869334cfa5c841 | /references/anatomic-location-json-schema.md | No. The schema file is machine-readable and must stay with its data. |
| 2026-09-21 | openimagingdata/findingmodel | .claude/skills/manage-anatomic-locations/reference/json-schema.md | 75afd39a400419dcfaf7c8d4a34f065b4d804e0d | /references/anatomic-location-json-schema.md | No. It is agent-facing curation guidance and belongs with the skill. |
| 2026-09-21 | openimagingdata/imaging-problem-list | sample_data/example2/xr_shoulder_20210522_efl.json | 36fa30c7383bf687d7bc17815282a93e123a56cb | /references/exam-finding-list-example.md | No. The sample data is test input; only an excerpt was migrated. |
| 2026-09-21 | openimagingdata/imaging-problem-list | sample_data/example2/MRN0000001_ipl.json | 36fa30c7383bf687d7bc17815282a93e123a56cb | /references/imaging-problem-list-example.md | No. The sample data is test input; only an excerpt was migrated. |
| 2026-09-21 | RSNA/ACR-RSNA-CDEs | notes/oifm-overview.md | 44836c19f4e025cf1684a015ed5cc63c29eaf7f3 | /references/oifm-overview-extract.md | Yes for the note copy. The upstream original at findingmodels prompts/overview.md is an authoring prompt and stays. |
| 2026-09-21 | RSNA/ACR-RSNA-CDEs | notes/oifm-metadata-fields.md | 44836c19f4e025cf1684a015ed5cc63c29eaf7f3 | /references/oifm-metadata-fields-extract.md | Yes for the note copy. The upstream gist can point here. |
| 2026-09-21 | openimagingdata/openimagingdata.org | schemas/schema_differences.md | fb431dfc81801a5a8e621c0e8bf2acd20f74be7d | /references/cde-schema-differences.md | Yes. The repository is lineage and the note is documentation, not fixture. |
| 2026-09-21 | openimagingdata/findingmodel | .claude/skills/manage-anatomic-locations/reference/laterality-conventions.md | 75afd39a400419dcfaf7c8d4a34f065b4d804e0d | /semantic-foundation/anatomic-locations/laterality-conventions.md | No. It is agent-facing curation guidance that the skill loads at runtime and it belongs with the skill; the skill file may add a pointer here. |
| 2026-09-21 | RSNA/ACR-RSNA-CDEs | CONTEXT.md | 44836c19f4e025cf1684a015ed5cc63c29eaf7f3 | /semantic-foundation/common-data-elements/next-generation-vocabulary.md | No. The sixteen term definitions are condensed into a table there and expanded individually in the glossary, but CONTEXT.md is the working glossary of an active branch and must stay with it. |
| 2026-09-21 | talkasab/anatomiclocations.org | docs/index.markdown (Roadmap section, exam type companion line) | 1f39fa45f621cef947a3f3ef1f869334cfa5c841 | /semantic-foundation/exam-types/overview.md | No, the roadmap line stays on the site; quoted only |
| 2026-09-21 | openimagingdata/med-ontology-lookup | docs/product-roadmap.md (domain profiles, LOINC/RSNA Radiology Playbook section) | a1fd3ae7ca6a28bb7e5af6838fe4167938084389 | /semantic-foundation/exam-types/existing-building-blocks.md, /semantic-foundation/terminologies/med-ontology-lookup.md | No, it is an active planning document in the repository |
| 2026-09-21 | openimagingdata/med-ontology-lookup | docs/project-review-and-proposal.md (six-phase delivery sequence, delegated authentication) | a1fd3ae7ca6a28bb7e5af6838fe4167938084389 | /semantic-foundation/terminologies/med-ontology-lookup.md | No, it is the repository’s governing design document |
| 2026-09-21 | openimagingdata/med-ontology-lookup | docs/plans/2026-09-05-github-issue-backlog.md | a1fd3ae7ca6a28bb7e5af6838fe4167938084389 | /semantic-foundation/terminologies/med-ontology-lookup.md | No, summarized only |
| 2026-09-21 | openimagingdata/med-ontology-lookup | docs/plans/2026-09-14-typed-provider-failures.md | a1fd3ae7ca6a28bb7e5af6838fe4167938084389 | /semantic-foundation/terminologies/med-ontology-lookup.md | No, design detail stays with the code |
| 2026-09-21 | openimagingdata/med-ontology-lookup | README.md, src/med_ontology_lookup/{config.py,detect.py,models.py}, skills/med-ontology-lookup/SKILL.md | a1fd3ae7ca6a28bb7e5af6838fe4167938084389 | /semantic-foundation/terminologies/med-ontology-lookup.md, /semantic-foundation/exam-types/existing-building-blocks.md | No, install and usage documentation stays with the code |
| 2026-09-21 | openimagingdata/imaging-problem-list | docs/anatomic-location-assignment-rules.md (exam-scoped region fallback, sided-exam laterality) | 36fa30c7383bf687d7bc17815282a93e123a56cb | /semantic-foundation/exam-types/overview.md, /semantic-foundation/exam-types/existing-building-blocks.md | No, the full rules migrate to /data-structures/anatomic-location-assignment-rules.md, owned by Phase 3 |
| 2026-09-21 | openimagingdata/imaging-problem-list | README.md (Exam Finding List LOINC requirement), CLAUDE.md (data standards) | 06f64a7893b444b761dc069ed86140a081195eac (main), 36fa30c7383bf687d7bc17815282a93e123a56cb (dev) | /semantic-foundation/exam-types/overview.md | No, summarized only |
| 2026-09-21 | openimagingdata/imaging-problem-list | sample_data//*_efl.json, viewer/data//ipl.json, viewer/data/exam_type_mappings.json, viewer/data/finding_region_mappings.json | 36fa30c7383bf687d7bc17815282a93e123a56cb | /semantic-foundation/exam-types/existing-building-blocks.md | No, data stays in the repository; counts and one example only |
| 2026-09-21 | RSNA/ACR-RSNA-CDEs | docs/next-gen-schema/00-current-understanding.md (Playbook governance and licensing) | 44836c19f4e025cf1684a015ed5cc63c29eaf7f3 | /semantic-foundation/exam-types/overview.md, /semantic-foundation/terminologies/ontologies-used.md | No, quoted only; the branch document stays in the CDE repository |
| 2026-09-21 | RSNA/ACR-RSNA-CDEs | notes/oifm-overview.md (finding scope matched to exam type) | 44836c19f4e025cf1684a015ed5cc63c29eaf7f3 | /semantic-foundation/exam-types/overview.md | No, already extracted to /references/oifm-overview-extract.md |
| 2026-09-21 | RSNA/RadLex | RadLex.owl (RID:Source Playbook provenance counts) | d53bd9c666ebaef280f82a4eed02e755a1552d30 | /semantic-foundation/exam-types/existing-building-blocks.md, /semantic-foundation/terminologies/ontologies-used.md | No, the ontology stays upstream; counts only |
| 2026-09-21 | openimagingdata/template_extraction | templates/ (281 RadReport template names) | 4d947d7e7557ce6187a35d592f8199d3abb673cf | /semantic-foundation/exam-types/existing-building-blocks.md | No, the corpus stays in the repository; described and linked |
| 2026-09-21 | openimagingdata/openimagingdata.org | schemas/schema_differences.md (LOINC as a permitted index code system, modality and body_parts) | fb431dfc81801a5a8e621c0e8bf2acd20f74be7d | /semantic-foundation/exam-types/existing-building-blocks.md, /semantic-foundation/terminologies/ontologies-used.md | Yes, repository is lineage; already extracted to /references/cde-schema-differences.md |
| 2026-09-21 | openimagingdata/findingmodels | defs/ (index code system counts across 2,382 definitions) | 4475ac1bcb591f1a0951b2082b59208def173a5d | /semantic-foundation/terminologies/ontologies-used.md | No, the corpus stays in the repository; counts only |
| 2026-09-21 | talkasab/anatomiclocations.org | data/body_parts.json (cross-reference code system counts) | 1f39fa45f621cef947a3f3ef1f869334cfa5c841 | /semantic-foundation/terminologies/ontologies-used.md | No, the dataset stays in the repository; counts only |
| 2026-09-21 | openimagingdata/findingmodel | notebooks/data/anatomic_locations_noembed.json (cross-reference code system counts), docs/finding-enrichment-implementation-plan.md | 75afd39a400419dcfaf7c8d4a34f065b4d804e0d | /semantic-foundation/terminologies/ontologies-used.md, /semantic-foundation/terminologies/med-ontology-lookup.md | No, counts and one status statement only |
| 2026-09-21 | openimagingdata.org (live site) | Data Model: Structure and Function, 2024-01-25 | fetched 2026-09-21 | /semantic-foundation/exam-types/overview.md | No, the site stays canonical |
| 2026-09-21 | openimagingdata/findingmodels | lists/README.md | a30c3c95fa3943e7340ce87575f4b1b926987eb8 | /semantic-foundation/finding-models/finding-taxonomies.md | No. The README sits beside the CSV files it describes and should stay with them; add a link here. Note the README’s own title names the author, which the bundle replaces with “MGB exam-oriented sub-taxonomies”. |
| 2026-09-21 | openimagingdata/findingmodels | CLAUDE.md | 4475ac1bcb591f1a0951b2082b59208def173a5d | /semantic-foundation/finding-models/content-catalog.md | No. It is agent-facing repository guidance and belongs with the code. Only the conventions were summarized. |
| 2026-09-21 | openimagingdata/findingmodels | docs/plans/definition_cleanup.md | 4475ac1bcb591f1a0951b2082b59208def173a5d | /semantic-foundation/finding-models/authoring-workflow.md | No. It is an active work plan; summarized only. |
| 2026-09-21 | openimagingdata/findingmodels | .claude/skills/finding-author/SKILL.md | 4475ac1bcb591f1a0951b2082b59208def173a5d | /semantic-foundation/finding-models/authoring-workflow.md | No. Agent skills are executable and stay with the repository. |
| 2026-09-21 | openimagingdata/findingmodels | .claude/skills/finding-batch/SKILL.md | 4475ac1bcb591f1a0951b2082b59208def173a5d | /semantic-foundation/finding-models/authoring-workflow.md | No. Agent skills are executable and stay with the repository. |
| 2026-09-21 | openimagingdata/findingmodels | .claude/skills/finding-review/SKILL.md | 4475ac1bcb591f1a0951b2082b59208def173a5d | /semantic-foundation/finding-models/authoring-workflow.md | No. Agent skills are executable and stay with the repository. |
| 2026-09-21 | openimagingdata/findingmodel | docs/finding-enrichment-prd.md | 75afd39a400419dcfaf7c8d4a34f065b4d804e0d | /semantic-foundation/finding-models/enrichment-pipeline.md | Yes, eventually. The document describes a superseded pathway and is already archived on the work edge; a pointer here would say so. |
| 2026-09-21 | openimagingdata/findingmodel | docs/enrichment-pipeline-optimization-proposal.md | 75afd39a400419dcfaf7c8d4a34f065b4d804e0d | /semantic-foundation/finding-models/enrichment-pipeline.md | No. It is a design analysis of the superseded pipeline; summarized only. |
| 2026-09-21 | openimagingdata/findingmodel | docs/canonical-structured-metadata-and-enrichment-rewrite.md | 1942b06a91d6a5c5eefe10f99a7273e41e24be01 | /semantic-foundation/finding-models/enrichment-pipeline.md | No, not while unmerged. Revisit when the branch lands. |
| 2026-09-21 | openimagingdata/findingmodel | docs/adr/0001, 0002, 0003 | 1942b06a91d6a5c5eefe10f99a7273e41e24be01 | /semantic-foundation/finding-models/enrichment-pipeline.md | No. Decision records belong with the code that implements them. |
| 2026-09-21 | openimagingdata/findingmodel | docs/metadata/enrichment/enrichment-agent-architecture.md | 1942b06a91d6a5c5eefe10f99a7273e41e24be01 | /semantic-foundation/finding-models/enrichment-pipeline.md | No. It names modules and functions and is code documentation. |
| 2026-09-21 | openimagingdata/findingmodels | docs/plans/metadata-enrichment-plan-history-2026-05-24.md | dcc6c4cfe9f359e5ae582f898ff3dbcf48a3be4f | /semantic-foundation/finding-models/enrichment-pipeline.md | No. It is branch-local review provenance. |
| 2026-09-21 | openimagingdata/FindingModelForge | docs/finding-model-creation-workflow.md | 15d9ebcf64734b889081feed4d645a0afca67e61 | /semantic-foundation/finding-models/authoring-workflow.md | Partly. The user-facing stages could point here; the HTMX implementation guidance stays with the code. |
| 2026-09-21 | openimagingdata/FindingModelForge | docs/DRAFT_WORKFLOW.md | 15d9ebcf64734b889081feed4d645a0afca67e61 | /semantic-foundation/finding-models/authoring-workflow.md | No. It documents the draft data model and caching behavior for developers. |
| 2026-09-21 | openimagingdata/imaging-problem-list | docs/anatomic-location-assignment-rules.md | 36fa30c7383bf687d7bc17815282a93e123a56cb | /data-structures/anatomic-location-assignment-rules.md | Yes. The rules are domain specification, not code documentation, and the coding pipeline can link here. |
| 2026-09-21 | openimagingdata/imaging-problem-list | docs/technical-imaging-findings.md | 36fa30c7383bf687d7bc17815282a93e123a56cb | /data-structures/technical-imaging-findings.md | Yes, once the ontology-coverage audit it calls for is done. The source is marked draft and its open items are still live, so keep both until then. |
| 2026-09-21 | openimagingdata/FindingModelForge | docs/finding-model-creation-workflow.md | 15d9ebcf64734b889081feed4d645a0afca67e61 | /applications/finding-model-forge.md | Partly. The four user-facing stages, the AI timeout budget, and the single-page HTMX behavior are summarized here; the testing patterns, selectors, and endpoint table stay with the code. |
| 2026-09-21 | openimagingdata/FindingModelForge | docs/DRAFT_WORKFLOW.md | 15d9ebcf64734b889081feed4d645a0afca67e61 | /applications/finding-model-forge.md | Partly. The draft object fields and the five-status lifecycle move here; the caching behavior and developer notes stay with the code. |
| 2026-09-21 | openimagingdata/FindingModelForge | docs/database.md | 15d9ebcf64734b889081feed4d645a0afca67e61 | /applications/finding-model-forge.md | No. Collection shapes and access patterns are code documentation; only the store choices were summarized. |
| 2026-09-21 | openimagingdata/FindingModelForge | tasks/done/PRD-public-draft-review.md | 15d9ebcf64734b889081feed4d645a0afca67e61 | /applications/finding-model-forge.md | No. A completed feature requirements document; summarized as the peer-review layer. |
| 2026-09-21 | openimagingdata/FindingModelForge | tasks/done/comments-feature-prd.md | 15d9ebcf64734b889081feed4d645a0afca67e61 | /applications/finding-model-forge.md | No. A completed feature requirements document; summarized as the peer-review layer. |
| 2026-09-21 | openimagingdata/FindingModelForge | tasks/model_iteration_feature_plan.md | af357f8decf029d99863ece63f03e1a7e86c18e5 | /applications/finding-model-forge.md | No, not while unmerged. Revisit when feature/model-editing lands. |
| 2026-09-21 | openimagingdata/FindingModelForge | zOld/plans/musings.md, Minisprint-2024-11.md, Minisprint-2025-01.md, Work_2025-04.md | f55dc858e1e3c3fde64ccd0d53b46ec07374ede6 | /applications/finding-model-forge.md | Yes, eventually. They are archived planning notes for the superseded application; a pointer here would preserve their substance. |
| 2026-09-21 | openimagingdata/imaging-problem-list | viewer/README.md | 06f64a7893b444b761dc069ed86140a081195eac | /applications/imaging-problem-list-viewer.md | Partly. The user-facing feature list moves here; the run and deploy steps stay with the code. Note the stale three-state status prose. |
| 2026-09-21 | openimagingdata/imaging-problem-list | DEPLOYMENT.md | 06f64a7893b444b761dc069ed86140a081195eac | /applications/imaging-problem-list-viewer.md | No. Wrangler and Cloudflare Pages steps are code documentation. |
| 2026-09-21 | openimagingdata/imaging-problem-list | docs/plans/viewer-v2-anatomy-dashboard.md | 36fa30c7383bf687d7bc17815282a93e123a56cb | /applications/imaging-problem-list-viewer.md | No, not while the plan is open. Revisit when viewer_v2 is reviewed and merged. |
| 2026-09-21 | openimagingdata/imaging-problem-list | README.md (dev) | 36fa30c7383bf687d7bc17815282a93e123a56cb | /applications/report-extraction-platform.md | Partly. The domain framing and the persistence model move here; provider setup, Taskfile commands, and CLI invocations stay with the code. |
| 2026-09-21 | openimagingdata/imaging-problem-list | CLAUDE.md (dev) | 36fa30c7383bf687d7bc17815282a93e123a56cb | /applications/report-extraction-platform.md | No. Agent-facing repository guidance; the six architecture notes were summarized. |
| 2026-09-21 | openimagingdata/imaging-problem-list | initial-extraction-plan.md | 36fa30c7383bf687d7bc17815282a93e123a56cb | /applications/report-extraction-platform.md | Yes, eventually. It is the original schema plan, already historical; a pointer here would say what survived. |
| 2026-09-21 | openimagingdata/imaging-problem-list | prompts/validator_prompt_example.md | 36fa30c7383bf687d7bc17815282a93e123a56cb | /applications/report-extraction-platform.md | No. The prompt is executable content that must track the code; the six problem types are mirrored here. |
| 2026-09-21 | openimagingdata/imaging-problem-list | docs/plans/extractor-evals-redesign.md | 36fa30c7383bf687d7bc17815282a93e123a56cb | /applications/report-extraction-platform.md | No. An active plan; the descope decision and its motivation are summarized. |
| 2026-09-21 | openimagingdata/imaging-problem-list | docs/archive/local-only-mode-hardening.md | 36fa30c7383bf687d7bc17815282a93e123a56cb | /applications/report-extraction-platform.md | No. A completed engineering plan naming modules and entry points. |
| 2026-09-21 | openimagingdata/imaging-problem-list | docs/coding-agent-design.md | 36fa30c7383bf687d7bc17815282a93e123a56cb | /applications/finding-and-location-coding.md | Partly. The five phases, the coding bundle schema, and the unresolved-reason vocabulary move here; model defaults, module map, and observability wiring stay with the code. |
| 2026-09-21 | openimagingdata/imaging-problem-list | docs/archive/finding-and-location-code-assignment-plan.md | 36fa30c7383bf687d7bc17815282a93e123a56cb | /applications/finding-and-location-coding.md | Yes, eventually. It is an archived superseded design; a pointer here would record what replaced it. |
| 2026-09-21 | openimagingdata/imaging-problem-list | docs/plans/anatomic-location-efl-ipl.md | 36fa30c7383bf687d7bc17815282a93e123a56cb | /applications/finding-and-location-coding.md | No, not while the Step 3b follow-on is open. |
| 2026-09-21 | openimagingdata/IPL-MVP-ExtractionAndLabeling | README.md | b06948fa417aeff0a6a4b97729c915b3ce5d5ed4 | /applications/ipl-mvp-extraction.md | Yes. The repository is lineage; its README is the only document and its substance, including the measured results and stated limitations, is now here. |
| 2026-09-21 | openimagingdata/IPL-MVP-ExtractionAndLabeling | FHIR_Example_Structure | 5ea6720e114d3e2cdded5c39ecc5a2eb108e97fb | /applications/ipl-mvp-extraction.md | Yes, eventually. A single unmerged design note with no code; its substance is recorded here. |
| 2026-09-21 | openimagingdata/openimagingdata.org (site) | /oidm-based-next-gen-reporting-assistance/ | live post, 2023-07-16 | /applications/reporting-sdk.md | No. The site post stays published; its architecture is summarized here. |
| 2026-09-21 | openimagingdata/findingmodels | docs/plans/definition_cleanup.md | 4475ac1bcb591f1a0951b2082b59208def173a5d | /roadmap/finding-model-content-direction.md | No. An open draft plan; its category counts and execution order are summarized here, the per-model examples stay with the repository. |
| 2026-09-21 | openimagingdata/findingmodels | lists/README.md (taxonomy-export-2026-08-15) | a30c3c95fa3943e7340ce87575f4b1b926987eb8 | /roadmap/finding-model-content-direction.md | No, already recorded against semantic-foundation/finding-models/finding-taxonomies.md. Only the triage statement is used here. |
| 2026-09-21 | openimagingdata/findingmodels | docs/cdestaging_ct_chest_batch_progress.md (content/chestcts) | 0472a4673fe476ec5335e6b3a1197faa70480426 | /roadmap/finding-model-content-direction.md | No, not while unmerged. A live batch tracking document. |
| 2026-09-21 | openimagingdata/findingmodel | docs/canonical-structured-metadata-and-enrichment-rewrite.md (feature/metadata-cleanup) | 1942b06a91d6a5c5eefe10f99a7273e41e24be01 | /roadmap/finding-model-format-evolution.md | Pending. The design document belongs with the branch until it lands; only its stated goals are here. |
| 2026-09-21 | openimagingdata/findingmodel | tasks/canonical-structured-metadata-implementation-plan.md (dev) | 504a42aad771926f5fb91fd69fe0b637f4aef211 | /roadmap/finding-model-format-evolution.md | No. An execution plan; only its slice status is recorded here. |
| 2026-09-21 | openimagingdata/findingmodel | tasks/schema-versioning-future.md | 75afd39a400419dcfaf7c8d4a34f065b4d804e0d | /roadmap/finding-model-format-evolution.md | No. A deferred task plan; its governing rule is quoted here. |
| 2026-09-21 | RSNA/ACR-RSNA-CDEs | notes/oifm-schema-v2-draft.md (next-gen-2026) | 44836c19f4e025cf1684a015ed5cc63c29eaf7f3 | /roadmap/finding-model-format-evolution.md | No. Itself a copy of an upstream gist; summarized as a stated direction. |
| 2026-09-21 | openimagingdata/imaging-problem-list | issue 1, “Create System of Data Models” | n/a (issue) | /roadmap/ipl-data-model-system.md | No. The issue stays open; its substance is quoted here. |
| 2026-09-21 | openimagingdata/imaging-problem-list | docs/plans/anatomic-location-efl-ipl.md, docs/anatomic-location-assignment-rules.md (dev) | 36fa30c7383bf687d7bc17815282a93e123a56cb | /roadmap/ipl-data-model-system.md | No. The assignment rules are separately migrated to /data-structures/; only the open follow-on is recorded here. |
| 2026-09-21 | talkasab/BodyPartIndex.py | TODO.md | 388ae0a6da92f5ee4cf36620bbeeabe223938471 | /roadmap/anatomic-locations-and-radlex.md | Yes, eventually. The list is reproduced with current status; a pointer here would preserve it if the repository moves to the organization. |
| 2026-09-21 | talkasab/anatomiclocations.org | docs/index.markdown (roadmap section) | 1f39fa45f621cef947a3f3ef1f869334cfa5c841 | /roadmap/exam-types.md, /roadmap/anatomic-locations-and-radlex.md | Partly. The exam type and site roadmap lines are recorded here; the rest of the page is site content. |
| 2026-09-21 | RSNA/ACR-RSNA-CDEs | docs/next-gen-schema/04-anatomy-gaps.md, 11-anatomy-axis.md (next-gen-2026) | 44836c19f4e025cf1684a015ed5cc63c29eaf7f3 | /roadmap/anatomic-locations-and-radlex.md | No, already recorded against semantic-foundation/anatomic-locations/radlex-integration.md. Only the structural requests are named here. |
| 2026-09-21 | openimagingdata/med-ontology-lookup | docs/product-roadmap.md | a1fd3ae7ca6a28bb7e5af6838fe4167938084389 | /roadmap/exam-types.md | No, already recorded against semantic-foundation/exam-types/. Only the Playbook implications are restated here. |
| 2026-09-21 | Gamma deck, January 2026 | whole deck | n/a (live) | /roadmap/roadmap-2026.md | No. The deck is extracted in full at /references/status-update-2026-01.md; the roadmap restates only its direction statements. |