Built for billing agencies that serve US healthcare.

How a billing agency uses ClaimVise.

You keep the client. You keep the contracts. You keep the supervisor seat. ClaimVise takes the routine work: eligibility checks, chart retrieval, first-pass coding, rule checks and charge entry. Your supervisors review every claim, clear the holds and decide when a charge is posted.

Nothing goes into a practice's billing system until a person clicks Post. If a connector hits something it does not recognize, it stops and tells you what happened and who should fix it.

One account, separate practices.

One agency account holds all of your practices. Each practice is kept apart from the others:

• Plan and wallet per practice. Each practice has its own monthly plan, included volume and prepaid wallet for overage, so you can see what each client costs.
• Modules per practice. Turn on Coding, Eligibility, OncoEMR retrieval and AdvancedMD posting only for the practices that use them.
• Setup per practice. Providers, locations, NPI and tax ID, contracted rates and billing rules are set for each practice, with payer-specific rules on top.
• Separation. Your practices, users and data are kept apart from every other agency. Inside your agency, users see only the practices they are assigned to.
• Roles. Agency admin, supervisor, coder and AR caller. Each role sees only what it needs.

Built for many specialties, proven first in hematology and oncology.

ClaimVise is built to work across specialties. The coding engine and the CMS reference data cover them all, so an agency with a mixed client list does not need a different tool for each practice. We began with hematology and oncology, where infusion billing is hardest. That is where our testing runs deepest, and where we are live with a billing-agency client. Their practices also include a cardiology practice that uses eligibility checks. Each new specialty gets its own rules and runs in shadow beside the standard result on the practice's own notes. A qualified coder must review and sign off the rules before routine use. Existing practices are not affected. If your agency has practices in other specialties, talk to us.

What your team gets.

• A practice switcher. The dashboard, claims queue and menus follow the practice you are working in.
• A dashboard with live counts, revenue and receivables for each practice.
• A team report that shows, per person, how many charts they retrieved, coded, reviewed, approved and posted.
• A Billing & Payments page with each practice's wallet, allowance used, overage and ledger.
• An encrypted vault for each practice's EMR, billing-system and eligibility-portal logins. Your administrators manage it.
• Claim review where you can reorder lines and edit. The audit trail keeps the original AI output next to every human change.
• Plain reasons on every connector queue, so a biller sees what went wrong and what to do without reading a log.
• Charge sheet. An agency admin can keep each practice's own charge amounts with start and end dates. A claim always uses the charge in force on its date of service.
• Billing scorecard. Every night, ClaimVise compares each claim three ways: as ClaimVise coded it, as your reviewer finalized it, and as the practice actually charged it (the practice's signed charges). You see trends over time, how each reviewer's edits compare, a claim-by-claim list, and which rules fired. The ClaimVise team switches it on for your agency, and your admins can open it.

Posting checks.

These features are built and in the platform. A person still clicks Post.

• A drug dispensed under several NDCs posts as one line per NDC, with the right modifiers.
• A plain-words "Ready for AdvancedMD posting?" report shows missing dispense or NDC data before claims reach the connector.
• If a hold was a wrong finding, a supervisor can release it by giving a written reason. The release is logged.

Rules that learn from your reviewers.

Reviewers often make the same fix again and again. When that happens, and the practice's own charges confirm the fix, ClaimVise can turn it into a rule for that practice. It is built and running, with tight limits:

• A rule can only remove a code or add a modifier from a short approved list.
• A rule never creates a billed code. It never touches a line a person has corrected. It switches itself off if reviewers reverse it.
• It is off by default for each practice. Admins can see and suspend any rule.
• Every use is marked on the claim and logged.

The learning happens in the rules. The AI model itself is not retrained on your data.

Reference data.

All the October 2026 CMS quarterly datasets are loaded, and the 15 HCPCS codes CMS ended on 30 September 2026 are closed.

Systems and integrations.

Live today: OncoEMR (chart retrieval), AdvancedMD (charge posting) and eTactics (eligibility). For any other EHR, upload notes as a PDF or image.

Planned: Availity (eligibility and claim submission), eClinicalWorks, OmniMD and Meditab. Planned means not live yet. Tell us which systems your practices use. That sets the order.

Pricing.

Each practice is priced one of two ways. You can mix models across your practices.

• Per practice, per month. Coding & Claim Readiness is ₹80,000 with 1,200 claims included, then ₹72 per claim. Eligibility Verification is ₹66,000 with 3,000 verifications included, then ₹25 per verification. Overage is drawn from the practice's prepaid wallet. On a monthly plan, any unused wallet balance expires at the start of each calendar month (India Standard Time) and does not carry forward. At full included volume that is about ₹67 per claim and ₹22 per verification.
• Per unit, pay as you go. ₹80 per claim for coding, claim readiness and posting, and ₹27 per verification, with no monthly plan fee. A pay-per-unit wallet does not expire. This usually suits smaller practices, below about 1,000 claims a month.

These prices follow the currency you pick in the pricing section on the homepage, which shows dollars by default. If you have many practices, talk to us about volume terms. A monthly server hosting fee of ₹7,000 / up to $175 per practice applies on top of the plan price.

Onboarding.

Getting started is setup, not a big implementation project.

1. Agreement and BAA. We sign the agency agreement and a Business Associate Agreement.
2. Account and first practice. We create your agency account and your first practice, and set the plan terms for each module.
3. Credentials and profile. Your administrator adds the practice profile and puts the practice's system logins in the vault.
4. First supervised batch. We run the first claims or worklist together, with a person reviewing every result, before the practice moves to routine use.

We give you a realistic timeline for your practices on the demo call.

What we ask in return.

Straight feedback on edge cases. The first weeks with a new agency always turn up specialty or payer patterns we have not seen. Your QA team knows them best. Tell us as soon as you see one, and we will add it to the rules for every customer.

Where your data is processed.

AI processing runs on AWS Bedrock in the US, under our executed AWS Business Associate Addendum. The HIPAA page lists the controls in place today and the infrastructure work planned next.

Get in touch.

Partnership questions go straight to Chirag, the founder. There is no sales gate. Email chirag@innodel.com with your agency name, your number of practices and your rough monthly claim volume. We reply within one business day with a side-by-side view for your operation.