The boundary of this market
Technology, clinical content, transaction infrastructure, and delegated services used to discover prior authorization requirements, assemble and exchange supporting documentation, conduct prospective or concurrent utilization review, communicate determinations, manage exceptions and appeals, and report operating performance.
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 revenue-cycle products with no maintained prior authorization capability evidence
- care-management platforms with no documented utilization review or authorization workflow
- clinical decision-support tools with no UM or authorization use case
- consultancies without a maintained technology, criteria, transaction, or delegated service offering
- payer portals listed as market providers when they are only access points for one payer's own requirements
- patient-specific medical or coverage advice
How the market divides
Delegated Specialty Utilization Management Organization
5 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 Utilization Management Workflow 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.
Clinical Criteria And Decision Support
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.
Provider-Side Authorization And Patient-Access Automation
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.
Payer-Provider Authorization Network And Clearinghouse
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.
Pharmacy Electronic Prior Authorization And Medication-Access Network
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.
FHIR Interoperability And Compliance Infrastructure
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.
Utilization Review Decision Intelligence
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.
Concurrent Review And Medical-Necessity Collaboration
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.
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.