Mapping Reconciliation

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

Solution archetype #

617

Problem family

Composition, Interface & Interoperability Failure

Problem subfamily

Protocol, Schema & Encoding Incompatibility

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.”

When This Archetype Applies

No catalog groundingNone of the structural conditions is currently represented by an accepted prime or domain-specific abstraction.

Diagnostic problem

Multiple actors, systems, standards, schemas, vocabularies, or models map one domain to another in incompatible ways, causing translation errors, semantic mismatch, duplicated work, interoperability failure, inconsistent reporting, or contested decisions.

What this problem means

The structural problem is a correspondence conflict. Local mappings may be reasonable inside their own context, but they become incompatible when systems or actors must interoperate. One team’s “active customer,” one jurisdiction’s “resident,” one dataset’s “completed event,” or one translation’s label may not match another team’s category even when the names appear similar.

Without reconciliation, downstream users see contradictory reports, failed integrations, duplicated work, unfair classifications, brittle conversions, and opaque exceptions. The system may appear to have a shared vocabulary while actually preserving several incompatible maps under the surface.

Show the applicability expression

Applicability expression5 distinct conditions

Differing system mappingsandDisputed crosswalkandMis-scoped mapped equivalenceandContradictory mapping tablesandRepeated manual reconciliation

Algebraic1∧2∧3∧4∧5

groundedpartly groundedopen

5 conditions, all required.

5Required in every casenumbered 1–5

These hold no matter which pattern applies.

1

Differing system mappings · open

Two interoperating systems use different field, category, or code mappings. more

and — also required

2

Disputed crosswalk · open

A crosswalk exists but organizations or standards dispute material correspondences. more

and — also required

3

Mis-scoped mapped equivalence · open

Downstream decisions fail because mapped equivalence is interpreted as broader, narrower, conditional, or unrelated. more

and — also required

4

Contradictory mapping tables · open

Migration, integration, merger, policy alignment, or reporting exposes contradictions among mapping tables or conceptual models. more

and — also required

5

Repeated manual reconciliation · open

Experts repeatedly repair mapping errors manually because no stable shared correspondence rule exists. more

Coverage

0 of 5 conditions grounded · 5 open.

Read the methodology · Download the trigger-logic data

Mechanisms / Implementations

• Crosswalk Reconciliation Workshop: A facilitated session where domain experts compare conflicting crosswalks, name conflict types, choose correspondences, and record exceptions.
• Schema Mapping Review: A structured review of field-to-field, class-to-class, type-to-type, or entity-to-entity mappings across systems or datasets.
• Ontology Alignment Session: A method for reconciling different conceptual models, category systems, or domain vocabularies that carve up reality differently.
• Mapping Conflict Matrix: A table that lists each contested source element, competing target mappings, conflict type, selected rule, decision, confidence, and exception status.
• Translation Memory Review: Reviews and reconciles competing phrase, label, concept, or terminology mappings across languages, teams, or historical translations.
• Code Crosswalk Validation: Tests reconciled mappings among codes, classifications, billing categories, diagnostic categories, policy categories, or product taxonomies.
• Standard-Setting Process: A formal governance process that resolves recurring mapping conflicts by creating or updating shared rules, standards, or reference mappings.
• Reconciliation Report: Documents decisions, unresolved conflicts, exceptions, tests, adoption guidance, and change impacts for a reconciled mapping.

Related Abstractions

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

Built directly on (3)

• Equivalence Relation: Groups elements into equivalence classes.
• Function (Mapping): Relates inputs to outputs.
• Relation: Describes associations or dependencies.

Also references 9 related abstractions

• Adjudication (Dispute Resolution): Dispute resolution.
• Data Integrity: Accuracy and consistency preserved.
• Delegation of Authority: Assign responsibility.
• Interoperability: Systems function together.
• Procedural Fairness (Due Process): Due process.
• Representation: Model complex ideas.
• Schema: Structured knowledge framework.
• Set and Membership: Groups and categorizes elements.
• Versioning: Tracks incremental changes over time.

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.

Editorial Notes

Problem Classification

Classification: Composition, Interface & Interoperability Failure → Protocol, Schema & Encoding Incompatibility

Problem kernel: incompatible cross-domain mappings create semantic conflict

Rationale: Earliest causal condition: Multiple actors, systems, standards, schemas, vocabularies, or models map one domain to another in incompatible ways, causing translation errors, semantic mismatch, duplicated work, interoperability failure, inconsistent reporting, or contested decisions.

Independent corroboration: The earliest necessary condition in the frozen evidence is: Multiple actors, systems, standards, schemas, vocabularies, or models map one domain to another in incompatible ways, causing translation errors, semantic mismatch, duplicated work, interoperability failure, inconsistent reporting, or contested decisions. That is a protocol schema and encoding incompatibility problem because Independently maintained formats, versions, schemas, codes, identifiers, units, and mappings cannot exchange meaning or reconstruct content reliably.

Review outcome: Independent reviewer agreement; high confidence.