Skip to content

Mapping Reconciliation

Resolve conflicts between competing mappings so systems, teams, or domains can interoperate or reason from a shared correspondence.

The Diagnostic Story

Symptom: Two systems claim to work from the same underlying data, but their outputs don't agree. Integration teams argue about whether the discrepancy is a data problem, a terminology problem, or a policy problem, and nobody can tell. Edge cases are quietly forced into approximate categories, creating hidden errors nobody tracks. When something goes wrong, audits reveal that different teams were using incompatible crosswalks and nobody had written that down.

Pivot: The structural problem is that local mappings were optimized for local contexts and never reconciled into a shared correspondence. The shift is to bring the competing mappings into a single explicit reconciliation process: compare correspondences, classify conflicts, decide resolution rules, and publish a versioned reconciled mapping that states its scope and preserves documented exceptions.

Resolution: Translation errors drop across systems, teams, and jurisdictions. Reports and classifications become consistent because actors use the same correspondence for the same defined purpose. Exceptions are visible rather than silently swallowed, and mapping decisions are traceable so downstream users can understand why a particular correspondence was chosen.

Reach for this when you hear…

[health informatics] “Three hospitals all say they report ICD codes but they've each mapped the same procedure to a different code, so our quality metrics are comparing apples to oranges.”

[supply chain integration] “Our product catalog uses SKUs, theirs uses GTINs, and there are about forty items where our crosswalk says they're equivalent but they actually aren't.”

[merger integration] “Both companies call it a 'customer' but the legal definitions are different enough that half our deduplication is creating duplicates instead of removing them.”

Mechanisms / Implementations

  • Crosswalk Reconciliation Workshop: This is a ritual mechanism.
  • Schema Mapping Review: This is a procedure mechanism.
  • Ontology Alignment Session: This is a method mechanism.
  • Mapping Conflict Matrix: This is a artifact mechanism.
  • Translation Memory Review: This is a procedure mechanism.
  • Code Crosswalk Validation: This is a test_or_assessment mechanism.
  • Standard-Setting Process: This is a institution mechanism.
  • Reconciliation Report: This is a document mechanism.

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (3)

Also references 9 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Schema Mapping Reconciliation · domain variant · recognized

Reconciles conflicting field, entity, type, state, or event mappings across data schemas or software systems.

Ontology Alignment Reconciliation · domain variant · recognized

Reconciles competing conceptual models or category systems so concepts can be compared without assuming perfect synonymy.

Crosswalk Reconciliation · implementation variant · recognized

Uses a crosswalk table or crosswalk process to resolve incompatible category, code, policy, or terminology mappings.

Terminology Mapping Reconciliation · communication variant · recognized

Reconciles competing term, label, phrase, or translation mappings so shared communication does not produce divergent action.