The Day 1 Data Problem: Standardizing Item Masters During Hospital Mergers
Why incompatible product data is the hidden barrier in healthcare M&A integration, and what it takes to turn two item masters into one shared language
The legal close of a hospital merger gets a lot of attention. Signing ceremonies, press releases, leadership announcements. What gets less attention is what happens on Day 1 when two supply chain teams try to operate as one organization and discover that their product data speaks entirely different languages.
Two ERPs can be connected. Two GPO agreements can be consolidated. Two purchasing teams can be reorganized under a single leader. But if the item masters behind those systems are not standardized, the integration is not real. The same surgical glove might be item number 00042 at one facility and item number SG-7814 at another. One system calls the manufacturer "Cardinal Health," the other calls them "Cardinal Health Inc." One catalog includes GTIN data; the other does not. Research from McKinsey & Company consistently finds that data integration failures are among the top drivers of unrealized synergy value in healthcare mergers, with supply chain systems identified as a primary source of post-merger operational friction.
The item master problem does not resolve itself over time. It compounds. Every day that two facilities operate from incompatible product catalogs is a day that contract savings go uncaptured, spend analytics produce misleading results, and operational teams work around a problem that the merger was supposed to eliminate.
The Scale of the Challenge: The average large health system merger brings together item masters with tens of thousands of records each, built over years across different ERP platforms, GPO relationships, and data governance practices. Reconciling them is not a cleanup task. It is a translation project that requires matching, enrichment, and governance infrastructure most organizations have never built before.
Why Connected Systems Are Not the Same as Integrated Data
Integration teams in healthcare M&A tend to focus on the systems: connecting ERPs, aligning EHR platforms, consolidating contract management tools. That work is necessary. But system connectivity does not produce data compatibility. Two systems that are technically linked can still contain fundamentally incompatible product records that prevent unified reporting, contract alignment, and operational consistency.
The item master sits at the root of all of it. It is the reference layer that purchasing workflows, inventory management, clinical documentation, and charge capture all depend on. When two merged organizations have item masters that describe the same physical products using different identifiers, different descriptions, and different attributes, every system built on top of those item masters inherits the incompatibility. Reports that should show enterprise-wide spend instead show two parallel views that cannot be reconciled. Contract compliance that should reflect combined purchasing volume instead reflects fragmented activity. A report from the Healthcare Financial Management Association (HFMA) found that supply chain integration delays in hospital mergers directly reduce the financial synergies the deal was projected to deliver, with data standardization identified as the most frequently cited bottleneck.
The gap between system integration and data integration is where most merger timelines slip and where most synergy projections fall short. Closing it requires treating product data standardization as its own workstream, not as a side effect of connecting the right systems.
What Incompatible Item Masters Actually Block
It helps to be specific about what breaks when two item masters remain unreconciled after a merger closes. The problems are not abstract. They show up in concrete operational failures that affect staff, finances, and patient care.
Unified Spend Reporting
Enterprise spend analytics require a common product reference. Without one, the same product appears under different identifiers across facilities, and aggregating spend by category, manufacturer, or contract becomes impossible without manual reconciliation. Leadership cannot see true enterprise purchasing volume, which means they cannot prove compliance with GPO commitments or leverage combined volume in vendor negotiations. The AHRMM Cost, Quality, and Outcomes (CQO) Movement has long identified unified product data as the prerequisite for meaningful supply chain analytics. In a merger context, that prerequisite is doubly critical because the financial case for the deal depends on demonstrating consolidated savings.
Contract Alignment and GPO Optimization
One of the primary financial rationales for hospital mergers is the ability to consolidate purchasing under more favorable contract terms. Achieving that requires knowing which products each facility is buying, from which suppliers, at which prices, under which contracts. When item masters describe the same products differently, contract matching fails and the savings remain theoretical.
Vendor name inconsistencies alone can prevent GPO contract compliance from being tracked accurately. If one facility's item master lists a supplier as "Becton Dickinson" and another lists them as "BD Medical," the system cannot recognize that both facilities are purchasing from the same manufacturer under the same GPO agreement. The Government Accountability Office has documented that contract compliance gaps in healthcare procurement are frequently driven by exactly this kind of identifier mismatch rather than deliberate non-compliance.
Operational Consistency Across Facilities
Merged facilities that cannot reference products through a shared catalog operate with persistent friction at the frontline. Clinicians transferring between facilities encounter unfamiliar product names and item numbers for products they use every day. Supply chain staff processing cross-facility transfers cannot match items without manual lookup. Recall notifications that should propagate across the entire enterprise stall at the facility boundary because the recalled item number at one location has no automatic connection to its equivalent at another.
Patient safety is not immune to these gaps. The FDA's MedWatch program documents cases where recall response times were extended because affected products could not be rapidly identified across all facilities where they had been purchased. A unified item master with shared product identifiers is what makes enterprise-wide recall response fast and reliable.
The Anatomy of a Merged Item Master Problem
Understanding what makes two item masters incompatible is the starting point for knowing what it takes to reconcile them. The challenges cluster around four areas that appear consistently in healthcare M&A integration work.
Different item numbering schemes. Each organization built its catalog using its own internal numbering logic. The same physical product has entirely different identifiers in each system, with no automated linkage between them.
Inconsistent manufacturer and supplier names. Vendor records were created independently over years, resulting in multiple name formats for the same supplier. Contract matching and spend aggregation both fail when the underlying manufacturer data is not normalized.
Uneven attribute completeness. One organization may have invested in enriching GTINs, UNSPSC codes, and clinical attributes. The other may not have. Merging two catalogs of unequal data quality requires enriching the gaps before a unified standard can be applied.
Duplicate products with no shared identity. Products that both organizations purchase may exist under completely different descriptions, classifications, and catalog numbers, with nothing in either system to indicate they are the same item. Identifying and linking those matches is the core technical challenge of item master reconciliation.
Each of these problems is solvable. None of them solve themselves, and none of them get easier the longer they are left unaddressed after the merger closes.
A Useful Frame: Think of two merged item masters as two dictionaries written in dialects of the same language. Individual words exist in both, but the spelling, format, and usage rules differ throughout. The goal is not to pick one dictionary and force everyone to use it. The goal is to build a translation layer that makes both catalogs readable as one.
What Standardization Actually Requires
Reconciling two item masters into a shared product catalog is a structured process that runs in parallel with broader merger integration work. The steps build on each other, and skipping any of them produces a result that looks unified on the surface but fails under operational pressure.
Step 1: Assess Both Catalogs Against a Common Standard
Before any matching or merging begins, both item masters need to be evaluated against the same data quality benchmark. Attribute completeness rates, GTIN coverage, UNSPSC classification accuracy, manufacturer name consistency, and HCPCS code validity against current CMS standards should all be measured for both organizations. The assessment reveals not just what the gaps are, but which organization's data provides a better starting foundation and where enrichment will be required before a unified catalog can be built.
Step 2: Match Products Across Both Catalogs
Product matching is the technical heart of item master reconciliation. The goal is to identify every instance where both organizations are purchasing the same physical product and create a shared product identity that both legacy item numbers can map to. This requires matching logic that goes beyond description similarity, using GTINs where they exist, GS1 global product identifiers, manufacturer catalog numbers, and clinical attribute comparisons to confirm equivalency with confidence rather than assumption.
High-confidence matches can be processed automatically. Lower-confidence matches and unmatched items require clinical and supply chain stakeholder review to confirm equivalency or identify true product differences. That review is what separates a technically matched catalog from a clinically validated one.
Step 3: Enrich to a Shared Data Standard
Once products are matched, both sets of records need to be enriched to meet a unified attribute standard. That means backfilling missing GTINs against FDA device registration data, updating classifications to current UNSPSC and HCPCS standards, normalizing manufacturer names against authoritative supplier reference data, and populating clinical attributes including sterility, implantable status, and country of origin across both catalogs.
Enrichment is also where substitute relationships get mapped across the merged catalog. Products that one organization had validated substitutes for can extend that intelligence to the other, and gaps where neither organization had substitutes mapped can be identified and prioritized before they become operational problems.
Step 4: Synchronize Across All Connected Systems
A unified product catalog only delivers value if every system that depends on product data draws from it. ERP procurement workflows, EHR clinical documentation, contract management platforms, inventory systems, and charge capture processes all need to reference the same shared product identities. Synchronization means mapping legacy item numbers from both organizations to the shared catalog and ensuring that updates to the unified record propagate automatically to all connected systems.
This is where the Healthcare Industry Resilience Collaborative's (HIRC) work on item-level normalization becomes directly relevant. HIRC's shared standards across more than 1,200 hospitals mean that health systems participating in the network can leverage existing normalization work rather than building equivalency mappings from scratch for every product category.
The Timeline Reality: Starting Before Day 1
The most important thing to understand about item master standardization in a hospital merger is that Day 1 is too late to start. The data work needs to begin during the pre-close integration planning period, running in parallel with system integration, contract consolidation, and operational planning.
Health systems that wait until after close to address item master incompatibility spend the first six to eighteen months of the merged organization managing workarounds rather than capturing synergies. Research published in Health Affairs found that supply chain integration timelines in hospital mergers correlate directly with the degree of pre-close data preparation, with organizations that invested in data standardization before close completing operational integration significantly faster than those that deferred it.
Pre-close data work does not require access to sensitive operational or financial information from either organization. It requires product catalog data, manufacturer records, and classification information, all of which can be shared and worked on under standard confidentiality agreements during the integration planning period. The output is a unified catalog that is ready to deploy on Day 1 rather than being assembled under operational pressure after it.
The Pre-Close Advantage: Organizations that begin item master reconciliation during integration planning arrive at Day 1 with a shared catalog ready to deploy. Organizations that wait arrive at Day 1 with the same two incompatible catalogs they had before the merger closed, plus the added pressure of a combined operation that needs both of them to work as one.
How Symmetric Health Solutions Serves as the Universal Translator
Symmetric Health Solutions provides the product intelligence, matching technology, and integration capabilities that turn two incompatible item masters into a shared operational language. The platform assesses both catalogs against a common data quality standard, applies matching logic that uses GTINs, GS1 global identifiers, manufacturer catalog numbers, and clinical attributes to identify equivalent products across both systems, and enriches matched records to a unified attribute standard using FDA registration data and authoritative manufacturer sources.
Legacy item numbers from both organizations map to shared product identities in the unified catalog, so existing purchasing workflows, clinical documentation, and ERP integrations continue to function while the merged organization transitions to a common reference. The translation layer means neither facility has to abandon its existing processes on Day 1. They both gain access to a shared catalog while their legacy systems catch up.
Post-merger, Symmetric's continuous enrichment engine keeps the unified catalog current as the merged organization grows, products change, and new facilities are added. As a member of HIRC, Symmetric's normalization work is grounded in shared standards across more than 1,200 hospitals, giving merged health systems a connection to industry-wide product intelligence rather than a catalog that exists in isolation.
The result is a post-merger integration that moves faster, captures synergies sooner, and rests on a data foundation the entire merged organization can trust from Day 1 forward.
