Skip to content

docs: remove outcome_domain taxonomy, add taxonomy mapping design#125

Merged
gilliankerr merged 5 commits intomainfrom
docs/taxonomy-panel-revisions
Feb 27, 2026
Merged

docs: remove outcome_domain taxonomy, add taxonomy mapping design#125
gilliankerr merged 5 commits intomainfrom
docs/taxonomy-panel-revisions

Conversation

@gilliankerr
Copy link
Contributor

Summary

  • Removes the 14-value outcome_domain taxonomy 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 success
  • Keeps MetricDefinition.category (7 values) unchanged for internal admin UI grouping
  • Adds TaxonomyMapping model to the Session 2 design — supports one metric → multiple external taxonomy codes with optional funder/partner context
  • Rewrites the phase prompt from a 66-line Session 1 draft to a comprehensive 5-session implementation guide with GK review gates and correct field specs
  • Adds "DO NOT hardcode an internal outcome taxonomy" anti-pattern to the DRR with full rationale

Files changed

File What changed
tasks/fhir-informed-data-modelling.md Phase F0 marked REMOVED, sequencing updated, risk table cleaned, presenting issues revised
tasks/phase-fhir-cids-prompt.md Complete rewrite — 5 sessions, correct field types, GK review gates, "pull main" reminders
tasks/design-rationale/fhir-informed-modelling.md New anti-pattern, revised taxonomy trade-off, updated graduated complexity path
TODO.md CIDS-META1 + CIDS-ORG1 task description updated, CIDS-CODES1 now includes TaxonomyMapping

Relationship 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

  • Verify no outcome_domain references remain in the three plan/prompt files (except in the "REMOVED" documentation)
  • Verify phase prompt Session 1 field specs match tasks/cids-json-ld-export.md Phase 1 fields (minus cids_theme, plus cids_theme_override)
  • Verify DRR anti-pattern section is consistent with implementation plan's Phase F0 REMOVED rationale
  • Close PR docs: expand FHIR+CIDS implementation prompt to all 5 sessions #123 after merge

🤖 Generated with Claude Code

gilliankerr and others added 5 commits February 27, 2026 14:45
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants