The boundary of this market
Organizations, networks, platforms, standards, and operating infrastructure used to exchange, normalize, route, secure, match, govern, and make electronic health information usable across organizational and system boundaries.
The maintained market is organized around operating role, documented capability, authority context, and the buyer decision each record can support. It is not a popularity list, paid marketplace, or claim that a single product category can own every part of the workflow.
What is outside the boundary
- general analytics products with no maintained exchange or interoperability capability evidence
- EHRs listed solely because they store clinical data, without a maintained exchange network or interoperability offering
- consultancies without a maintained platform, network, terminology, identity, or exchange service
- patient-specific access, privacy, coverage, or clinical advice
- thin directories that conflate standards support with conformance or production availability
How the market divides
Qualified Health Information Network
11 maintained organizations begin with this operating model. Their dossiers preserve adjacent capability, fit conditions, and evidence limits so the primary classification does not erase meaningful differences.
Health Information Network And Exchange Framework
1 maintained organizations begin with this operating model. Their dossiers preserve adjacent capability, fit conditions, and evidence limits so the primary classification does not erase meaningful differences.
Enterprise Interoperability And Integration Platform
7 maintained organizations begin with this operating model. Their dossiers preserve adjacent capability, fit conditions, and evidence limits so the primary classification does not erase meaningful differences.
FHIR Server, API, And Compliance Platform
4 maintained organizations begin with this operating model. Their dossiers preserve adjacent capability, fit conditions, and evidence limits so the primary classification does not erase meaningful differences.
Payer Interoperability And API Platform
3 maintained organizations begin with this operating model. Their dossiers preserve adjacent capability, fit conditions, and evidence limits so the primary classification does not erase meaningful differences.
Clinical Data Network And Record-Retrieval Platform
4 maintained organizations begin with this operating model. Their dossiers preserve adjacent capability, fit conditions, and evidence limits so the primary classification does not erase meaningful differences.
Identity, Consent, And Patient-Matching Platform
2 maintained organizations begin with this operating model. Their dossiers preserve adjacent capability, fit conditions, and evidence limits so the primary classification does not erase meaningful differences.
Terminology And Semantic-Interoperability Platform
3 maintained organizations begin with this operating model. Their dossiers preserve adjacent capability, fit conditions, and evidence limits so the primary classification does not erase meaningful differences.
Community And Public-Health Exchange Infrastructure
1 maintained organizations begin with this operating model. Their dossiers preserve adjacent capability, fit conditions, and evidence limits so the primary classification does not erase meaningful differences.
Cloud Health-Data Platform
3 maintained organizations begin with this operating model. Their dossiers preserve adjacent capability, fit conditions, and evidence limits so the primary classification does not erase meaningful differences.
Point-Of-Care Network And Event-Notification Platform
2 maintained organizations begin with this operating model. Their dossiers preserve adjacent capability, fit conditions, and evidence limits so the primary classification does not erase meaningful differences.
Why the architecture matters
Buyers often compare organizations that participate in the same broad outcome but own different stages, data, authority, or accountability. A platform, data provider, network, service organization, content provider, and integration layer may all appear in one workflow without being substitutes. The market map makes those relationships visible.
The durable evaluation question is not which organization has the longest feature list. It is which operating model fits the buyer's governed work, which dependencies it introduces, what evidence it preserves, how change propagates, and whether the organization can exit or replace the system without losing the decision record.
How to use this publication
- Use categories and the market map to define the operating role.
- Use capability pages to define workflows and evidence requirements.
- Use authority and risk-domain records to establish scope and questions requiring qualified judgment.
- Use organization dossiers and comparisons to build a research list.
- Use guides and tools to create a repeatable evaluation record.