For billing & RCM teams
Different clients. One dependable reference.
Keep the Medicare benchmark straight across client locations, code lists, and schedule reviews. Spend less time chasing a number and more time answering the question.
Look up a Medicare rateFeeBase / 2026
Urgent care
Quick reference
| Code | Name | Price |
|---|---|---|
| 99202 | New patient · level 2 | $85.27 |
| 99203 | New patient · level 3 | $133.65 |
| 99204 | New patient · level 4 | $200.98 |
| 99213 | Established patient · level 3 | $107.63 |
| 99214 | Established patient · level 4 | $153.27 |
| 93000 | EKG with interpretation | $17.58 |
Medicare reference · Manhattan
Non-facility · September 2026 · Non-QP
Source details
Rates checked September 14, 2026. CMS RVU26C, ZIP 10001, April 2026 geography. Base Medicare amounts before claim adjustments. Names are plain-language labels.
Make the client handoff the easy part.
A client asks why a fee changed. You need more than the new amount: the prior rate, the right locality, and a source you can point to.
- Answer the one-code question
- Check a code while the question is still in front of you. Set the ZIP, date, and care setting, then see the rate and its source.
- Review the whole client list
- Move from an individual lookup to a fee-sheet update built around that client’s codes and location.
- Send a clear comparison
- Put the old and new rates in one view so the next conversation starts with what changed.
01
02
03
Location, handled
You know your ZIP. We’ll find the locality.
Medicare uses payment localities, not just city or state names. Enter the practice ZIP and FeeBase looks up the match—one less detail to research before you get to the rate.
Some ZIPs cross locality boundaries. When more detail is needed, add ZIP+4 to narrow the match.
Try your ZIPA location match in FeeBase
01
Your practice ZIP
10001
02
CMS payment locality
Manhattan, NY
03
The reference for your location
Ready for your code list
The matched locality stays with the result, so your whole list uses the same geographic basis.
For billing & RCM teams
The next client shouldn’t mean starting from scratch.
One practice needs an annual refresh. Another opens a location. A third asks why a familiar code has a different Medicare reference. The details change; the work repeats.
01
Onboard a practice
Establish a dated Medicare reference for the everyday codes at that client’s location.
02
Refresh an existing client
Identify changes before replacing the reference the team uses. Keep items that need attention visible.
03
Answer the rate question
Trace an individual amount back to the settings and release behind it. Keep the answer with the client’s context.
Checked before you use it
Current rates. Clean data. A source behind every number.
Your team needs a reference it can trust. FeeBase checks CMS releases before they reach the lookup, and keeps the source with the result.
Inside our data- The right release for the date
- Your service date selects the applicable fee schedule. Historical releases stay available, so a past rate doesn’t quietly become today’s rate.
- Validated before it reaches your workflow
- Release versions, source files, and imported records are checked before a dataset is accepted for lookup.
- An answer you can verify
- The rate keeps its CMS release and locality mapping. See the geography date too, including when an earlier mapping was used.
01
02
03
Fee sheets / $149 per update
One code list. One cleaner update.
Current rates, a clear comparison, and a printable reference for your team.