Revenue cycle · Deep learning medical coding
Fathom
Fathom is a deep-learning medical coding automation company for health systems and RCM partners. It is coding AI, not ambient documentation and not patient-pay software.
Strong fit
- Health systems and RCM partners that want deep-learning autonomous coding at chart scale
- Coding leaders measuring auto-code rate, denial rate, and coder FTE change
- Buyers comparing AI coding vendors rather than only outsourcing more charts
Weak fit
- Clinics that only need online patient statements
- Organizations without coding leadership to own exception queues
- Buyers that need plan-side prior auth criteria tools instead of coding
Bottom line
Fathom earns a Recommend for autonomous medical coding driven by deep learning. Co-founded and led by CEO Andrew Lockhart, the company sells coding automation to health systems, physician groups, and RCM vendors that want machines to draft codes with humans on exceptions. Third-party estimates put revenue roughly in a $25-45M band, above the prefer $5-50M center but under the $500M hard cap. Implementation needs clean documentation feeds and coding-ops ownership. Pricing is enterprise. Score sits just under CodaMetrix on this board when coding automation is the core buy.
Score breakdown
Weights: Outcomes 35% · Product 30% · Implementation 20% · Pricing clarity 15%.
Fathom is a medical coding automation company co-founded by CEO Andrew Lockhart. Providers and RCM partners use deep learning models to draft codes from clinical documentation and leave exceptions for human review.
It is coding AI, not ambient documentation and not patient-pay software. Compare CodaMetrix when contextual autonomous coding is the peer frame, Nym when professional-fee automation is enough, and SmarterDx when post-note CDI capture matters more than full code production.
Score reflects credible coding automation with enterprise commercial opacity.
Competitor landscape
| Vendor | Overall | Ease of implementation |
|---|---|---|
| SmarterDx | 7.6 | 7.2 |
| CodaMetrix | 7.6 | 7.3 |
| Fathom | 7.5 | 7.2 |
| Inbox Health | 7.4 | 7.1 |
| Collectly | 7.4 | 7.2 |
| MDaudit | 7.4 | 7.1 |
| Enter Health | 7.3 | 7.0 |
| Candid Health | 7.2 | 6.9 |
| Aptarro | 7.0 | 6.8 |
| PatientPay | 7.0 | 7.0 |
| Mentaya | 6.9 | 7.0 |
| MD Clarity | 6.9 | 6.7 |
| Nym | 6.6 | 6.4 |
| Rivia Health | 6.5 | 6.4 |
Pricing
| Item | Detail |
|---|---|
| Model | Enterprise SaaS / managed coding automation; quote-based. |
| What usually drives cost | Chart volume, specialty coverage, service mix, and integration depth. |
| What to ask in diligence | Unit or platform pricing at your monthly coded chart volume, including exception-handling model. |
| Published pricing | No public list price. |
Prerequisites for purchase
| Need | Why it matters |
|---|---|
| What you need to get Fathom to function | |
| Coding ops owner named | Automation stalls without owners. |
| Chart volume and specialty mix documented | Vague SOWs waste model training. |
| Baseline coder FTE and denial rates | You cannot judge ROI blind. |
| Security and BAA path clear | AI coding stalls in InfoSec. |
| Exception SLA defined | Humans must clear the leftovers. |
| What will maximize your value | |
| Start with one service line | Big-bang coding flips fail loudly. |
| Publish weekly auto-code dashboards | Keep leadership honest. |
| Train coders on exception patterns | Otherwise they rework everything. |
| Deal-breakers | |
| Patient-pay portal only | |
| No EHR documentation access | |
| No coding leadership | |
Value creation time frame
| # | Stage | Typical range |
|---|---|---|
| 1 | Security review | 3-6 weeks |
| 2 | Pilot service line | 6-12 weeks |
| 3 | Expand specialties | 4-10 weeks |
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.