What Interoperability Means in a Healthcare Media Data Flow
The four kinds of interoperability in healthcare media data flows (syntactic, semantic, identity, and operational) and how each breaks.
The short answer
In healthcare IT, interoperability usually refers to clinical data exchange through standards like HL7 FHIR and the USCDI. Healthcare media has its own interoperability problems, even though it rarely uses those standards. Data moves between the brand, agencies, DSPs, data providers, and measurement partners. Each handoff can lose meaning.
Breaking interoperability into four types makes problems easier to find.
1. Syntactic interoperability
Can the systems read each other's files? This is about formats: CSV versus JSON, field names, date formats, encoding. A target list sent with NPIs stored as numbers may lose leading zeros. A date in the wrong format may be read as a different day.
Common failure: a partner silently drops rows it cannot parse.
2. Semantic interoperability
Do both systems mean the same thing by the same field? "Specialty" might mean primary taxonomy in one system and a vendor-assigned specialty in another. "Impression" might mean served in one report and viewable in another. "Reach" might count devices or people.
Common failure: two reports that appear to agree are measuring different things.
3. Identity interoperability
Can both systems identify the same person, provider, or household? Different partners use different identity graphs. An NPI list matched by one partner may connect to different devices than the same list matched by another. Exposure recorded in one system may not link to outcomes in another.
Common failure: exposures are lost between activation and measurement, lowering Rx match rates.
4. Operational interoperability
Do the processes around the data work together? Who sends updated lists, how often, and who confirms receipt? When a partner changes a field definition, who is notified?
Common failure: a list is updated in one system but not another, so campaigns target stale audiences.
A handoff checklist
| Check | Question |
|---|---|
| Format | Is there a written file specification? |
| Definitions | Is there a data dictionary shared by all partners? |
| Identity | Which identifier links records across systems? |
| Row counts | Are counts confirmed at each handoff? |
| Versioning | Is every file dated and versioned? |
| Change control | Who approves changes to definitions or formats? |
Build a shared data dictionary
The most useful single step is a data dictionary: every field used across partners, its definition, its source, and its owner. It takes a few hours to draft and prevents many hours of reconciliation. Include definitions for reach, impression, match, and each outcome metric.
Practical takeaway
Map every data handoff in your campaign on one page. For each, note the file format, identifier, definition source, and owner. Confirm row counts at every step for the first flight.
Sources
External guidance and platform documentation change. Links were current at publication; check them again before relying on them for a decision.
Editorial note. Analysis and frameworks are the author's own and do not represent Acxiom or any current or former employer, client, or named platform. Examples labeled hypothetical or illustrative are not results from real campaigns. Nothing here is legal, regulatory, or medical advice.
New pharma programmatic breakdowns, occasionally
One email when I publish something worth reading. Benchmarks, measurement teardowns, and case studies with the caveats attached. No cadence promises, no reselling your address.
Unsubscribe any time. See the privacy policy.
Working through this decision on a real plan?
I work on health and pharma data, identity, and activation, after five years running HCP and DTC programmatic agency-side. Happy to talk through how this applies to your situation.