Exchange reliability and data-quality research agenda
A measurement framework for availability, routing, match quality, completeness, semantic fidelity, latency, exceptions, and receiving-workflow use without inventing a universal score.
A measurement framework for availability, routing, match quality, completeness, semantic fidelity, latency, exceptions, and receiving-workflow use without inventing a universal score.
The maintained dataset joins 41 organization records, 21 normalized capabilities, 11 operating models, 18 authority records, and 10 operating domains. Counts describe the research corpus; they are not a market-size or quality score.
The market architecture
Qualified Health Information Network
11 maintained organizations are classified in this model. The primary classification describes where the offering begins; adjacent scope remains in each dossier.
Health Information Network And Exchange Framework
1 maintained organizations are classified in this model. The primary classification describes where the offering begins; adjacent scope remains in each dossier.
Enterprise Interoperability And Integration Platform
7 maintained organizations are classified in this model. The primary classification describes where the offering begins; adjacent scope remains in each dossier.
FHIR Server, API, And Compliance Platform
4 maintained organizations are classified in this model. The primary classification describes where the offering begins; adjacent scope remains in each dossier.
Payer Interoperability And API Platform
3 maintained organizations are classified in this model. The primary classification describes where the offering begins; adjacent scope remains in each dossier.
Clinical Data Network And Record-Retrieval Platform
4 maintained organizations are classified in this model. The primary classification describes where the offering begins; adjacent scope remains in each dossier.
Identity, Consent, And Patient-Matching Platform
2 maintained organizations are classified in this model. The primary classification describes where the offering begins; adjacent scope remains in each dossier.
Terminology And Semantic-Interoperability Platform
3 maintained organizations are classified in this model. The primary classification describes where the offering begins; adjacent scope remains in each dossier.
Community And Public-Health Exchange Infrastructure
1 maintained organizations are classified in this model. The primary classification describes where the offering begins; adjacent scope remains in each dossier.
Cloud Health-Data Platform
3 maintained organizations are classified in this model. The primary classification describes where the offering begins; adjacent scope remains in each dossier.
Point-Of-Care Network And Event-Notification Platform
2 maintained organizations are classified in this model. The primary classification describes where the offering begins; adjacent scope remains in each dossier.
Why role comes before feature
Several organizations can mention the same broad outcome while owning different data, authority, workflow stages, services, or accountability. Comparing them through a flat checklist conceals those boundaries. The architecture starts with the operating model, then uses capabilities and evidence states to identify true overlap.
Market tensions to examine
Integrated breadth can reduce handoffs but increase configuration and migration scope. Specialist depth can improve one workflow but create dependencies at boundaries. Maintained content and data can make a platform more actionable but introduce licensing, provenance, latency, and exit questions. Service delivery can transfer work but not the buyer's accountability for oversight and outcomes.
Methodology
- Define the market boundary, exclusions, operating models, and capability taxonomy before classifying organizations.
- Require an approved official source for organization inclusion and each documented capability.
- Keep authority sources, provider claims, independent observations, editorial synthesis, and unknowns in separate evidence states.
- Use one primary operating model per organization while retaining adjacent scope in the narrative record.
- Preserve source URLs, review dates, material changes, limitations, and correction history.
Limitations
- The maintained population is substantial but not claimed to be a complete global market.
- Official public documentation may omit available capabilities or lag product and service changes.
- Documented positioning does not measure product depth, configured availability, independent performance, implementation effort, customer outcome, or commercial terms.
- Authority mappings are editorial research aids and do not establish buyer-specific applicability or product conformity.
- No organization may purchase inclusion, classification, finding, or correction outcome.
Reproducibility and updates
The report is reproduced from the provider registry, normalized facts and evidence, authority and domain records, and the publication taxonomy. A material change requires a dated source and editorial explanation. Historical values remain available through the change ledger rather than disappearing when the current record changes.
Research boundary
Health Interoperability Review provides market, standards, policy, and operating research. It does not provide patient-specific medical advice, determine an individual's rights or coverage, certify product conformity, authorize a disclosure, or replace legal, privacy, security, clinical, or implementation review.