For reimbursement consultants
Give every recommendation a reference.
Bring a traceable Medicare benchmark to your reimbursement analysis. Keep the rates, assumptions, and source releases together from first calculation to client discussion.
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 number easy to defend.
When a client asks where a benchmark came from, the answer should be on the page. Preserve the service date, locality, and source alongside your comparison.
- Anchor the analysis
- Use the same location, date, and setting across your code list for a consistent Medicare comparison.
- Keep the evidence close
- Trace the calculation to its CMS release and geography mapping without reconstructing the research later.
- Make the handoff simple
- Bring a readable reference and a clear comparison to the client conversation.
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 reimbursement consultants
Spend the review on your recommendation.
A client brings a code list and asks what changed. Before you can advise them, you need a consistent benchmark: the right dates, the right locality, and a clear account of exceptions.
01
Annual fee review
Show the Medicare changes for the services the client uses. Separate movement in the reference from the business decision.
02
Negotiation preparation
Establish a dated Medicare benchmark alongside the client’s contracted rates. Make the comparison basis explicit.
03
Operational handoff
Leave a reference the billing team can use after the engagement ends, with the assumptions intact.
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.