NEW
Also known as: Crosswalk, Mapping Table
Codelists that map equivalent values across multiple classification schemes, standards, or systems.
DESCRIPTION
Cross-reference lists translate codes between schemes (e.g., industry or medical classifications). They support integration, migration, and reporting alignment by preserving semantics across contexts. Effective lists include many-to-one rules, versioning, and provenance. They often complement canonical models and global IDs. Stewardship ensures mappings remain authoritative and auditable.
ALTERNATIVE DEFINITIONS
Wikipedia
In metadata, a crosswalk is a mapping of the elements, semantics, and syntax from one schema to another.
Highlights schema-to-schema mapping central to cross-reference lists.
Wikipedia
Data mapping is the process of creating data element mappings between two distinct data models.
Emphasizes element-level mapping underpinning code translation.
RELATED TERMS
Cross-Reference Data Mapping Canonical Data Model Reference Data Code Tables Knowledge Representation Simple Knowledge Organization System Global ID Class Hierarchy Entity Resolution
COMPETING TERMS
Simple Reference List Canonical Code List
KNOWLEDGE AREAS
Data Integration & Interoperability Reference & Master Data Semantic & Knowledge Modeling Data Management
TARGET AUDIENCE
Data Steward Data Modeler Data Architect Data Engineer BI Specialist
EXTERNAL SOURCES
- Wikipedia - Crosswalk (metadata)
- U.S. Census Bureau - Industry code crosswalks
- U.S. National Library of Medicine - UMLS mappings across vocabularies
- W3C - SKOS mapping properties
TOP QUESTIONS
Why are Cross-Reference Lists necessary?
They translate codes between standards, enabling interoperable analytics, migrations, and regulatory reporting.
Category: Relevancy
How do Cross-Reference Lists differ from Simple Reference Lists?
Cross-reference lists map between schemes with complex rules; simple lists validate codes within one scheme.
Category: Opinion
What governance is needed for Cross-Reference Lists?
Include versioning, provenance, approval workflows, and impact analysis for changes.
Category: Requirements
What’s a common mistake with Cross-Reference Lists?
Ignoring many-to-one mappings or context, leading to ambiguous or incorrect translations.
Category: Mistakes
What risks arise from outdated Cross-Reference Lists?
Misclassification, wrong metrics, and failed compliance submissions can occur.
Category: Risk
How do SKOS mappings help Cross-Reference Lists?
SKOS provides mapping properties (exactMatch, closeMatch) to express equivalence with semantic clarity.
Category: Example
Where to start building Cross-Reference Lists?
Identify target and source schemes, establish mapping rules with domain experts, and publish with metadata and APIs.
Category: Requirements
What tools support Cross-Reference List management?
MDM systems, data catalogs, and semantic tools manage mappings with lineage and governance.
Category: Example
How do Cross-Reference Lists relate to canonical models?
They are a practical bridge when full canonical alignment is infeasible or incremental.
Category: Opinion