Revenue cycle · Autonomous medical coding
Nym
Nym is an autonomous medical coding engine that assigns billing codes from clinical documentation for supported specialties and routes exceptions to human coders.
Strong fit
- Health systems and large physician groups with large coding queues in the emergency department or other supported specialties
- Health records leaders who track coding cost per chart, turnaround, and how well codes hold up in audits
- Groups willing to keep people reviewing exceptions while automated coding takes the first pass
Weak fit
- Small practices with too little coding volume for an automated engine to pay off
- Buyers who need patient billing or denial recovery more than automated coding
- Teams unwilling to check specialty coverage before signing for several years
Bottom line
Nym is worth considering for health systems and large physician groups that want to automate medical coding in supported specialties, such as emergency department charts, with a clear audit trail. It suits coding teams prepared to run the rollout as a health records operations project. Organizations that want AI across more of the revenue cycle may prefer AKASA, and programs centered on coding audits may prefer MDaudit.
Score breakdown
Weights: Outcomes 35% · Product 30% · Implementation 20% · Pricing clarity 15%.
Nym uses an automated engine to assign medical codes from clinical notes. Charts it can code cleanly go straight to billing, and exceptions go to human coders for review. Large health systems that use it report faster emergency department coding and the ability to move coders to other work.
Nym covers coding only, so a patient payment platform or a full denials suite has to come from another vendor. The company has raised substantial funding. Setup is a health records operations project that runs over several weeks, and Nym quotes prices for each customer.
Among the billing tools we review, Nym scores below AKASA and Collectly, mainly because automated coding covers a narrower part of billing and each customer has to confirm coverage for its own specialties.
AKASA suits buyers who want generative AI across more of the billing process, and MDaudit suits organizations whose main need is coding and billing audits.
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 |
| RapidClaims | 7.1 | 7.5 |
| Nym | 6.6 | 6.4 |
| Aidéo Technologies | 6.6 | 6.8 |
Pricing
| Item | Detail |
|---|---|
| Model | An automated medical coding engine sold to health systems and physician groups, priced by quote. |
| What usually drives cost | Chart volume by specialty, accuracy guarantees, and connections to coding and billing systems. |
| What to ask before you buy | Cost per automatically coded chart compared with what coders cost you now, with covered specialties listed clearly. |
| Published pricing | No price list is posted on Nym's website, and each customer gets a quote. |
Prerequisites for purchase
| Need | Why it matters |
|---|---|
| What you need to get Nym to function | |
| Confirmed coverage for the specialties in your charts | Nym codes only the specialties it supports, so other charts stay with human coders. |
| Health records and coding leaders agreed on where exceptions go | Even with automation on the first pass, someone has to own the exceptions it sends back. |
| A clean connection to the EHR or coding system | Manual chart exports slow coding down and introduce errors. |
| A plan to audit samples of automatically coded charts | Regular audits of automatically coded charts show whether the codes hold up. |
| Your coding cost and turnaround today | Without today's figures, there is no way to measure what automation saves. |
| What will maximize your value | |
| Track cost per chart, turnaround, and coding-related denials | Faster coding can hide accuracy problems unless coding-related denials are tracked too. |
| Keep skilled coders on exceptions and complex specialties | Coders can move to other work, but complex charts still need experienced people. |
| Expand one specialty at a time | Adding specialties one at a time shows where the engine performs well before it handles everything. |
| Review audit trails with compliance monthly | Audit trails help only when compliance staff read them regularly. |
| Shut down duplicate manual coding queues once results check out | Keeping a manual coding queue running alongside the engine cancels out the savings. |
| Deal-breakers | |
| Your volume is too low to pay for an automated engine. | |
| Needed specialties are not supported. | |
| Health records staff will not review exceptions. | |
| There is no way to connect it. | |
| Leaders forbid audit sampling. | |
Value creation time frame
| # | Stage | Typical range |
|---|---|---|
| 1 | From signing to kickoff | 2-6 weeks for security review and setting up claims or chart data feeds |
| 2 | From kickoff to first use | 6-14 weeks for the first specialty or facility |
| 3 | From first use to steady results | 3-6 months before recovery or coding results level off |
Leadership
Recent news
- September 2026: Nym appeared on TIME's list of the World's Top HealthTech Companies for the second year in a row.
- April 2026: Nym appointed Lori M. Jones as CEO. She has more than two decades of experience scaling healthcare technology companies.
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.
