Market position and operating model
Xsolis provides a payer-provider utilization-management platform focused on admission status, concurrent authorization, medical necessity, discharge planning, case management, and denial prevention.
Xsolis is included because concurrent review and admission-status workflows are a substantial UM market adjacent to, but operationally different from, prospective outpatient prior authorization.
The primary classification describes where Xsolis begins in the buyer's operating problem. It does not imply that every module, jurisdiction, workflow, integration, service, or data dependency is interchangeable with another organization in the same category. Buyers should confirm the exact product, edition, service boundary, and accountable party included in a proposal.
Who should evaluate Xsolis
Hospitals and health plans seeking shared data and decision support for admission status, concurrent review, and payer-provider medical-necessity alignment.
A strong evaluation begins with a real scenario and its exception path. Ask the organization to identify inputs, authoritative content, configured rules, decision owners, handoffs, evidence retained, exports available, and the behavior when required data is missing or contradictory.
Documented capability record
| Capability | Evidence state | What remains to verify |
|---|---|---|
| Clinical Documentation Assembly Open provider-specific evidence record → | Documented in approved official positioning | Depth, package, configuration, data dependency, and production behavior require further verification. |
| Nurse And Physician Review Workflow Open provider-specific evidence record → | Documented in approved official positioning | Depth, package, configuration, data dependency, and production behavior require further verification. |
| Decision Support And Auto-Approval Rules | Documented in approved official positioning | Depth, package, configuration, data dependency, and production behavior require further verification. |
| Denial Reason And Correspondence | Documented in approved official positioning | Depth, package, configuration, data dependency, and production behavior require further verification. |
| Appeals And Peer-To-Peer Workflow | Documented in approved official positioning | Depth, package, configuration, data dependency, and production behavior require further verification. |
| Concurrent Review | Documented in approved official positioning | Depth, package, configuration, data dependency, and production behavior require further verification. |
| Metrics And Turnaround Reporting | Documented in approved official positioning | Depth, package, configuration, data dependency, and production behavior require further verification. |
| Audit Trail And Decision Provenance | Documented in approved official positioning | Depth, package, configuration, data dependency, and production behavior require further verification. |
Known evidence limits
Official prediction, ROI, and customer-scale claims are company-reported. The product's scope should not be generalized to pharmacy ePA or all pre-service authorization workflows, and medical necessity remains subject to payer and clinical review.
A documented capability means a current official source supports relevant positioning. It is not an independent observation of configured behavior, accuracy, completeness, latency, usability, implementation effort, integration depth, support quality, customer outcome, or legal and regulatory fitness. Missing public evidence remains not established; it is not silently converted into feature absent.
Enterprise demonstration agenda
- Confirm the precise product, edition, service, geography, and customer population under evaluation.
- Trace one representative case from intake through decision, exception, evidence retention, reporting, and downstream exchange.
- Repeat the workflow with missing data, a conflicting rule or record, a changed authority source, and a user override.
- Identify which content, interpretation, configuration, integration, review, approval, and validation responsibilities remain with the customer or another party.
- Export the decision history and reconcile it to the governing source, configured version, user action, timestamps, and affected records.
Questions to take into diligence
- Which named workflows and capabilities are available in the proposed package today?
- Which authority, content, data, or network dependencies are maintained by the provider, a partner, or the customer?
- How are changes detected, assessed, tested, approved, released, and preserved historically?
- What implementation roles, controlled configurations, integrations, migrations, and ongoing services are required?
- What can an auditor, regulator, clinical reviewer, compliance owner, or operational leader reconstruct from the exported record?
Source and research record
The dossier uses 14 normalized record elements and 1 linked evidence records internally. Those operational totals are not presented as a quality score. The decision-relevant public record is the claim, its source, evidence class, scope, and limitation.
- Xsolis Dragonfly utilization managementofficial-provider · monitored monthly