Skip to main content
Partitions are read-optimized views over MDM data from one or more sources. They draw from collections that have gone through entity resolution and reconciliation, delivering deduplicated and normalized records. Each partition declares:
  • Which resources and relationships are exposed — Each collection entry specifies the property schema and source mappings that describe how MDM output maps to the partition’s indexed fields.
  • Reconciliation strategies — How conflicting attribute values are merged (latest, earliest, aggregated, or custom logic).
  • Cross-source joins — Unified relationships let you traverse across systems without denormalizing the data first.
  • Traversal rules — Which related properties can be projected into the query context. Learn how this powers filtering in Traversed property filters.
  • Governance — MDM policies ensure that only curated, steward-approved data feeds downstream applications.

​
Traversed properties

Traversal rules let you bring attributes from related resources or contained structures into the current query scope. That enables filters such as “clinics that offer a related service with code cardiology” without copying data. Traversals are explicit and bounded, which keeps query plans predictable and prevents accidental fan-out.

​
Keep exploring

Partitions

Understand how records are reconciled before hitting downstream apps.

Traversed properties

Learn how to project adjacent resource attributes directly into partition search.