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 billing partners that want AI to code large numbers of charts on its own
- Coding leaders who track how many charts are coded automatically, denials, and changes in coder staffing
- Buyers comparing AI coding vendors instead of only sending more charts to an outside firm
Weak fit
- Clinics that only need online patient bills
- Organizations with no coding leader to own the charts AI cannot code
- Buyers that need health plan tools for prior authorization rules, not coding
Bottom line
Fathom is worth using for health systems, physician groups, and revenue cycle vendors that want deep learning to code charts automatically, with people handling exceptions. It suits teams with clean documentation feeds and a coding owner. Buyers focused on catching diagnoses after the note may prefer SmarterDx.
Score breakdown
Weights: Outcomes 35% · Product 30% · Implementation 20% · Pricing clarity 15%.
Fathom is a medical coding automation company co-founded and led by CEO Andrew Lockhart.
Providers and billing partners use its deep learning models to draft codes from clinical notes. Charts it cannot code are left for people to review. It is coding AI, not a note-taking scribe or patient payment software.
Setup needs clean clinical notes flowing in and a clear owner in coding operations.
Prices are quoted for each customer and are not published.
Among revenue cycle tools we review, Fathom scores just below CodaMetrix when coding automation is the main purchase.
CodaMetrix is the closest comparison for automated coding that uses context from the chart. Nym fits when automating physician fee coding is enough, and SmarterDx fits when catching missed diagnoses after the note matters more than producing every code.
Competitor landscape
| Vendor | Overall | Ease of implementation |
|---|---|---|
| SmarterDx | 7.6 | 7.2 |
| CodaMetrix | 7.6 | 7.3 |
| Fathom | 7.5 | 7.2 |
| Charta Health | 7.5 | 7.5 |
| MDaudit | 7.4 | 7.1 |
| Arintra | 7.2 | 7.1 |
| Maverick Medical AI | 7.2 | 7.1 |
| XpertDox | 7.0 | 7.0 |
| Nym | 6.6 | 6.4 |
Pricing
| Item | Detail |
|---|---|
| Model | Software or a managed coding service for large organizations, with quoted prices. |
| What usually drives cost | How many charts you code, which specialties are covered, which services you buy, and how deeply it connects to your systems. |
| What to ask before you buy | The price per chart or for the platform at your monthly chart volume, and how charts it cannot code are handled. |
| Published pricing | Fathom does not publish a price list. |
Prerequisites for purchase
| Need | Why it matters |
|---|---|
| What you need to get Fathom to function | |
| A named coding operations owner | Automation stalls with no owner. |
| Your chart volume and specialties written down | Vague work orders waste the time spent training the model. |
| Starting coder staffing and denial rates | You cannot judge the return without a starting point. |
| A clear path through security review and the business associate agreement | AI coding stalls in security review. |
| A set deadline for charts that need a person | People have to finish what the AI leaves. |
| What will maximize your value | |
| Start with one clinical department | Switching all coding at once fails badly. |
| Share weekly reports on automatic coding | Keep leadership honest. |
| Teach coders the kinds of charts the AI leaves for them | Otherwise they rework everything. |
| Deal-breakers | |
| You only need a patient payment portal | |
| It cannot get clinical notes from the EHR | |
| No coding leader | |
Value creation time frame
| # | Stage | Typical range |
|---|---|---|
| 1 | Security review | 3-6 weeks |
| 2 | Test in one department | 6-12 weeks |
| 3 | Expand specialties | 4-10 weeks |
Leadership
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 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.