Diagnostics & imaging AI · Clinical AI governance
Ferrum Health
Ferrum Health is a clinical AI governance platform for health systems. It helps teams manage, monitor, and deploy multiple AI models with site-specific performance evidence. It is not a single radiology detection algorithm.
Strong fit
- Health systems deploying many clinical AI models that need governance and monitoring
- Imaging and clinical leaders measuring model drift, site-specific performance, and ROI evidence
- Teams that want one pathway to validate and deploy third-party and homegrown models
Weak fit
- Buyers seeking a single radiology detection algorithm as the product
- Clinics with no AI deployment roadmap
- Organizations that will not staff clinical AI ownership after go-live
Bottom line
Ferrum Health earns a Conditional for health systems that already run, or plan to run, multiple clinical AI tools and need governance, monitoring, and deployment fabric more than another point algorithm. Customer quotes emphasize site-specific validation and easier multi-model integration. Product sits beside Aidoc and Rad AI as infrastructure rather than a competitor detection engine. Implementation needs cloud or on-prem pathway decisions and clinical owners. Pricing is unpublished and scale is earlier than category imaging leaders. Score reflects a real governance need with thinner public outcomes proof than mature detection vendors.
Score breakdown
Weights: Outcomes 35% · Product 30% · Implementation 20% · Pricing clarity 15%.
Ferrum Health is a clinical AI governance platform. Health systems use it to manage a model hub, monitor performance and drift, and deploy algorithms through a governed pathway while keeping PHI in chosen environments.
It is not a single radiology finding algorithm. Compare detection and reporting vendors like Aidoc, Rad AI, and Viz.ai when the buy is a clinical AI application; use Ferrum when the problem is operating many of those tools safely.
Conditional score reflects a clear governance niche with earlier public scale than the imaging AI leaders on this board.
Competitor landscape
| Vendor | Overall | Ease of implementation |
|---|---|---|
| Ferrum Health | 6.8 | 6.5 |
| Aidoc | 7.9 | 7.5 |
| Rad AI | 7.7 | 7.2 |
| Viz.ai | 7.7 | 7.3 |
| AISAP | 7.0 | 6.6 |
| Subtle Medical | 7.2 | 6.8 |
Pricing
| Item | Detail |
|---|---|
| Model | Clinical AI governance and deployment platform sold to health systems; quote-based. |
| What usually drives cost | Number of models and sites, observability scope, and cloud versus on-prem deployment choices. |
| What to ask in diligence | Cost to govern your current AI portfolio, with monitoring and new-model onboarding fees separated. |
| Published pricing | Public list price: not published. |
Prerequisites for purchase
| Need | Why it matters |
|---|---|
| What you need to get Ferrum Health to function | |
| An owned clinical AI portfolio or near-term deployment plan | Governance platforms need models to govern. |
| Clinical and IT sponsors for AI performance reviews | Unowned drift alerts go unread. |
| Decision on cloud, on-prem, or existing workflow pathways | Deployment fabric choices block go-live. |
| Data access path that keeps PHI in approved environments | Sovereignty requirements must be explicit. |
| Success metrics for model safety, performance, and ROI | Without metrics, governance becomes shelfware. |
| What will maximize your value | |
| Start by monitoring models already in production | Proof on live cohorts builds trust faster than greenfield only. |
| Review drift alerts with clinical service-line owners | IT-only review misses care impact. |
| Use one governed pathway for new model onboarding | Side-door integrations recreate the original mess. |
| Publish site-specific performance to the clinicians who use the tools | Hidden dashboards do not change behavior. |
| Expand model count only after monitoring SLAs are stable | Scale without observability multiplies risk. |
| Deal-breakers | |
| You only want a single radiology detection algorithm. | |
| You have no AI models and no plan to deploy any. | |
| Clinical leaders will not review performance evidence. | |
| Security will not approve a governed deployment pathway. | |
| You expect Ferrum to replace Aidoc-style detection products entirely. | |
Value creation time frame
| # | Stage | Typical range |
|---|---|---|
| 1 | Contract signed → kickoff | 3-8 weeks (security, PHI pathway, model inventory) |
| 2 | Kickoff → first live workflow | 8-16 weeks to monitor or deploy first governed models |
| 3 | First live workflow → steady value | 3-6 months before multi-model operations feel routine |
Methodology
| Weight | Factor | What it measures |
|---|---|---|
| 35% | Customer outcomes | Whether buyers get measurable operational or clinical-workflow results after go-live |
| 30% | Product | Capability depth, reliability, and fit for the job the category actually buys |
| 20% | Implementation | How hard it is to stand up, integrate, train, and stabilize |
| 15% | Pricing clarity | Whether a buyer can model total cost without a mystery quote |
| Label | Meaning |
|---|---|
| Highly recommend | Strong outcomes and product with manageable caveats |
| Recommend | Solid fit for the right buyer; know the tradeoffs |
| Conditional | Only with a specific use case or heavy caveats |
| Not recommended | Avoid for most buyers in this category |
Read our full methodology for how we weight scores and assign recommend labels.