docs: remove outcome_domain taxonomy, add taxonomy mapping design#125
Merged
gilliankerr merged 5 commits intomainfrom Feb 27, 2026
Merged
docs: remove outcome_domain taxonomy, add taxonomy mapping design#125gilliankerr merged 5 commits intomainfrom
gilliankerr merged 5 commits intomainfrom
Conversation
Taxonomy panel (4 experts, 3 rounds) concluded that a hardcoded 14-value outcome_domain taxonomy will fail because every funder, partner, and collaboration uses different outcome classification systems. The nonprofit sector has tried taxonomy standardisation for years without success. Changes: - Phase F0 (Unified Outcome Domain) marked as REMOVED with rationale - MetricDefinition.category (7 values) kept unchanged for UI grouping - outcome_domain removed from MetricDefinition, Program, PlanTarget - CIDS theme derivation simplified to two tiers (iris_metric_code lookup + admin override) until taxonomy mapping layer in Phase 2 - Sequencing table updated: Step 1 is now "CIDS 1" not "F0 + CIDS 1" - Risk table cleaned up, reporting queries updated - Phase F4 (Presenting Issues) updated to use category instead Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Complete rewrite of the implementation prompt incorporating: - Taxonomy panel decision: no outcome_domain, keep category as-is - TaxonomyMapping model in Session 2 for multi-funder taxonomy support - Correct field types (cids_has_baseline is CharField not BooleanField) - Complete OrganizationProfile fields (legal_status, sector_codes, website) - GK review gates on Sessions 1, 3, 4 - "Pull main" reminder on every session - Quick reference section explaining what was removed and why Supersedes the 66-line draft from PR #123. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Adds "DO NOT hardcode an internal outcome taxonomy" anti-pattern based on taxonomy panel (4 experts, 3 rounds, unanimous). Records GK's confirmation that sector-wide taxonomy standardisation has been attempted and failed. Updates: - New anti-pattern section with full rationale - Revised trade-off: outcome_domain → taxonomy-neutral platform - Risk registry: replaced taxonomy coarseness risk with mapping complexity risk - Graduated complexity: removed "Unified Outcome Domain taxonomy" from Phase 1, added taxonomy mapping layer Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Revised task descriptions to reflect taxonomy panel decisions: - CIDS-META1 + CIDS-ORG1: no longer includes outcome_domain or FHIR-DOMAIN1 — category stays unchanged - CIDS-CODES1: now includes TaxonomyMapping model for multi-funder taxonomy support Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add "cids_theme and cids_impact_theme are superseded" warning to Session 1 reading list (prevents AI sessions from building wrong fields from CIDS plan) - Add "theme derivation incomplete until Session 2" note to Session 1 scope boundaries - Make Session 2 TaxonomyMapping requirements-based instead of prescriptive (let implementing session choose GenericFK vs explicit FK pattern) - Note that TaxonomyMapping is new (not from original CIDS plan) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
4 tasks
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
outcome_domaintaxonomy from the FHIR implementation plan, phase prompt, and DRR — based on a 4-expert taxonomy panel that confirmed GK's feedback: every funder, partner, and collaboration uses a different outcome taxonomy, and the sector has tried standardisation for years without successMetricDefinition.category(7 values) unchanged for internal admin UI groupingTaxonomyMappingmodel to the Session 2 design — supports one metric → multiple external taxonomy codes with optional funder/partner contextFiles changed
tasks/fhir-informed-data-modelling.mdtasks/phase-fhir-cids-prompt.mdtasks/design-rationale/fhir-informed-modelling.mdTODO.mdRelationship to PR #123
PR #123 (from the other worktree session) expanded the phase prompt to 5 sessions but predates the taxonomy panel decision. This PR supersedes it — PR #123 should be closed after this one merges.
Test plan
tasks/cids-json-ld-export.mdPhase 1 fields (minus cids_theme, plus cids_theme_override)🤖 Generated with Claude Code