The platform
Four modules on one operating layer.
Resova iQ connects provider readiness, the encounter, the claim and the payer response — sitting across the systems you already run instead of replacing them.
Inside the product
What you work in, every day.
One login for the four sides of the practice. The three-minute walkthrough below shows the real interface running all four.
See it run
Watch the 3-minute demo.
What you get
Clinical, revenue, operations, compliance.
Behavioral health billing, credentialing and clinical documentation on one operating layer. Each module is useful alone; the value compounds because they share one record of what is true about a provider, an encounter, a payer and a claim.
Clinical iQ
An ambient AI scribe captures the visit, returns a structured draft for review, and writes the note back to your EHR once a provider signs. Encounter history stays searchable, and Rx Medguard puts psychiatry-specific medication reference — conversions, dose limits, tapering, special populations — alongside the work.
RCM iQ
Daily clinic readiness, eligibility verification and patient-responsibility checks, claim review and 837P submission, then denial management and appeals — with 277 acknowledgements and 835 remittances folded back into a claim lifecycle you can actually see. Every claim carries a version history with who changed what.
Operations iQ
Medical-records requests, practice performance reporting, provider directories and identifiers, and provider onboarding — the day-to-day machinery of running a multistate group, in one view instead of five spreadsheets.
Compliance iQ
Provider credentialing and payer enrollment tracking, payer contract management, telehealth prescribing law for all 51 US jurisdictions, and the audit trail. Payer rules your team authors are structured triggers and effects the platform can execute — not prose in a wiki nobody reads.
Reference data
Coding rules that are current, and provably so.
Claim checks are only as good as the tables behind them. Ours ship with the platform, carry a checksum against their published source, and fail a test when they drift out of date.
Sourced from CMS, CDC/NCHS, NUCC, NLM and NPPES. CPT® content is used under license from the American Medical Association.
Your payer contracts
Your contracts become rules the system can run.
Most practices cannot answer “what should this payer have paid us?” without opening a PDF. We read your executed contracts and turn the terms into checks that run against real claims.
Terms, not just rates
Timely filing windows, appeal levels and deadlines, prompt-pay terms, recoupment lookback, telehealth terms, prior-auth requirements and carve-outs — not only the fee schedule.
27 term typesRates as they really work
The same code can pay differently by modifier, credential tier, place of service and date. Rates are modeled that way, including percent-of-Medicare bases tied to a benchmark year.
qualifier-awareEvery term cites its source
Each extracted fact carries the sentence and its location in your PDF, verified by code against the document. You can check any of it without taking our word for it.
provenance on every factAmbiguity blocks, it does not guess
Unverified extractions cannot be accepted and ambiguous tables stop for a human. Rules arrive as drafts and only take effect once your team approves them.
fail-closedWorks with your stack
We connect to your EHR and clearinghouse. We don't replace them.
Chart context in, finalized notes back, 837P claims out, 277 and 835 in. Your system of record stays your system of record, and nothing here requires a migration.
Tell us what you run. If a connector does not exist yet we will say so, and tell you what a scoped deployment would look like in the meantime.
Getting started
What the first six months look like.
A scoped deployment, not a platform transformation. You do not replace the EHR and you do not rebuild the billing operation on day one.
Days 1–14 — connect and baseline
Connect the EHR and clearinghouse, load your executed payer contracts, and measure your current clean-claim rate, denial rate and days in A/R. That baseline is what everything later gets judged against.
Days 15–30 — configure and pilot
Review the rules derived from your contracts, set approval thresholds and routing, and run a scoped work queue in parallel with your existing process so nothing is at risk.
Days 31–180 — run and measure
Move the pilot queue into production, work exceptions through the platform, and measure each cycle against your baseline — long enough to see the clean-claim rate hold, not just spike.
Questions we get
The things buyers actually ask.
No. Resova iQ connects to the EHR you already use — reading chart context and writing finalized notes back. You keep your system of record and we fit around it. Today that connector exists for CharmHealth; Epic, athenahealth and eClinicalWorks are in development.
It includes one. Clinical iQ provides ambient AI documentation — the visit is captured, a structured draft comes back for review, and the finalized note writes to your EHR once a provider signs. But a scribe on its own does not get you paid. What makes the note valuable here is that it feeds claim readiness, so documentation that will not support the code is caught before submission rather than after denial. If ambient documentation is all you need, a standalone scribe will be cheaper. Resova iQ is for groups that want the note connected to credentialing, eligibility, coding and payment.
No. Clinical output stays provider-signed, and claims go out only under the approvals you configure. The platform prepares, flags and routes work; a person makes every decision that leaves your practice.
Any generative model can produce incorrect output, so we do not rely on trust. Notes are human-signed. Coding and claim checks are deterministic rules rather than model judgment. Contract facts are verified against the source document by code. Prompts and model versions are tracked, and changes pass regression evaluation before promotion. We are also candid that some safeguards are still being strengthened as we take on external deployments.
Capture is automated; promotion is not. We record the context, the recommendation, the correction a person made and what happened afterward. Turning that into a rule, test or guardrail is a reviewed step. This is a governed improvement system, not a model rewriting itself in production.
Models, speech-to-text and document AI sit behind interfaces rather than being wired through the workflow. Swapping one is a configuration change, not a rebuild, and your records, rules, audit trail and workflow state are unaffected.
Your notes, transcripts and records are yours — structured, portable and exportable. Nothing about the platform is designed to hold your data hostage.
Every action is traceable, overrides are recorded in an append-only ledger with a named person and a written reason, and historical state is retained so a record can be reconstructed as it stood on the date of service. See Security & Trust for the detail.
Pricing depends on provider count, modules and claim volume, so we quote it rather than publishing a list price. Tell us your numbers in the form and we will give you a real range on the first call.
Talk to us
See it against your own claims.
Send your provider count, states, EHR and claim volume and we will show you the platform running on problems that look like yours.