Home/Integrations/EHR/ICANotes
For behavioral health practices using ICANotesYour Notes Are Thorough. Are They What the Payer Asks For?
Medical necessity denials are not a verdict on how complete a note is. They turn on whether the record contains the specific things one payer's policy looks for. Keep ICANotes. Find out which payers are asking for something you are not saying.
Start with the free CareVixis practice assessment. No email required.
Your Notes Are Genuinely Thorough.
ICANotes is built around the note, and the documentation it produces is more complete than most practices manage.
Thorough Is Not the Same as Matching.
A payer is not grading the quality of your clinical thinking. It is checking whether a particular element is present, in a particular place, supporting a particular code.
A longer note does not automatically contain it.
So the Claim Fails on a Detail.
The care was right, the note was careful, and the denial cites something nobody thought was in question.
Then it is appealed one claim at a time and the same detail catches the next one.
We Read the Denial Against the Note.
CareVixis records which element each payer actually asked for and how often that is what failed, so a recurring denial becomes a billing problem you can fix once.
Keep ICANotes.
Nothing here asks you to document differently for a payer's benefit. ICANotes stays, and the denial gets explained rather than appealed blind.
Keep ICANotes. Find out what the payer is actually asking for.
Everything below is the evidence for what you just read.
What ICANotes publishes about its own platform, where a careful note still loses the claim, a ten-question framework you can put to any billing company, and the source for every fact on this page. If you have what you came for, you can stop here.
If my notes are thorough, why am I still getting medical necessity denials?
Because the payer is not grading completeness. It is checking its own criteria for this service, at this frequency, for this diagnosis, for this member. A note can be detailed, compliant and clinically excellent and still not contain the particular elements that one policy looks for.
That distinction matters because the usual response to a medical necessity denial is to document more. More is not the same as what was asked for, and a practice can add work indefinitely without the denial rate moving.
ICANotes Is Built Around the Note
Most EHRs treat documentation as a form. ICANotes treats it as the product. Everything below is ICANotes' own published description.[1]
| What it does | How ICANotes describes it |
|---|---|
| Built for behavioral health | "Built for mental health, not adapted from a general medical EHR", and "designed exclusively for behavioral health clinicians". |
| Menu-driven documentation | A platform that "combines menu-driven documentation with advanced features", with template-driven efficiency. |
| Certification | An "ONC Cures Certified platform" providing "ONC-certified charting". |
| In one platform | Charting, "integrated billing, telehealth, and scheduling". |
| Provenance | "Developed by behavioral health professionals", founded in 1999. |
Structured, consistent documentation is genuinely valuable, and it is why audits tend to go better for practices using it. Consistency and payer-specific sufficiency are simply two different things.
Where a Good Note Still Loses the Claim
Each of these produces a denial that looks like a documentation problem. Only some of them are one.
The payer wanted a specific element
A functional impairment statement, a symptom severity marker, a treatment response note. Present in some policies, absent from others, rarely named in the denial.
Time is billed but not evidenced the way the payer wants
Time-based psychotherapy codes turn on documented time. Payers differ on how, and where, they expect to see it.
The treatment plan is stale
Plans have review intervals. An out-of-date plan can undermine every claim in a period, all at once, retroactively.
Frequency exceeded an unstated limit
Weekly is routine until a policy says otherwise. The denial reads as medical necessity when the real issue is a frequency rule.
The template says the same thing every week
Efficient documentation can look repetitive to a reviewer. The care was individual; the record has to show that it was.
It was never a documentation problem
Eligibility, enrollment dates, a carve-out or a coding mismatch, arriving under a reason code that sends everyone to the chart. Weeks are spent improving notes that were fine.
That last one is the expensive one. A misread denial costs twice: the revenue, and the clinical time spent fixing something that was never broken. Establishing which of the six it is, before changing anyone's workflow, is the entire argument for root cause analysis.
Where This Fits Around What You Already Run
An illustration of the general flow for a practice keeping ICANotes, not a description of any specific configuration.
- ICANotesThe encounter is documented, coded and billed from the record.
- Clearinghouse and payerThe claim is transmitted and adjudicated, or rejected before adjudication.
- The remittance comes backPayment, adjustment, denial and patient responsibility, with the payer's reason and remark codes.
- VixisIQ™Where appropriate data can be obtained and normalized, denials are grouped by payer, clinician, diagnosis, service and time, which is how a documentation pattern becomes visible.
- VixisTrace™One denial is investigated properly, including the question of whether it is a documentation problem at all.
- A change worth making, and only thenClinical time is the scarcest thing in the practice, so a workflow change is proposed only once the cause is established.
What Should an ICANotes Practice Ask a Billing Company?
Nine questions for whoever bills for you now, and for CareVixis. The documentation ones are where this practice type is most often let down.
-
Can they tell a documentation denial from one wearing its costume?
Ask how they establish that a medical necessity denial really is about the record before anyone is asked to write more.
-
Do they read payer medical policy, or just resubmit?
Ask what a specific payer requires for a specific service, and see whether an answer exists.
-
Do they group denials by clinician and by payer?
A pattern in one clinician is a training question. The same pattern across all of them is a policy question. Very different fixes.
-
Who watches treatment plan review dates?
Ask what catches a stale plan before it invalidates a quarter of claims.
-
What happens the third time the same denial arrives?
Ask for a root cause they found, what changed, and how they knew it worked.
-
Will they work inside ICANotes?
Ask what they need from it and what changes if you keep it. CareVixis treats keeping ICANotes as a supported outcome.
-
How much clinician time will this cost?
Any proposal that starts with "document more" should come with evidence that documentation is the actual cause.
-
What will you see without asking?
Then the harder version: what would have told you a payer had changed its criteria last quarter?
-
Is the work performed in the United States?
Ask about subcontractors as well as staff. CareVixis is 100% US based and does not outsource.
Using ICANotes? Keep It.
Your clinicians are fast in it and your documentation is consistent because of it. That is worth protecting, and a migration would answer none of the questions on this page.
Keeping your system is a supported outcome, not a fallback. If you later want to move to the CareVixis platform, that move may be offered at no additional migration charge. Keeping the EHR you already have carries no monthly software fee from CareVixis.
Keep ICANotes. Find out what the payer is actually asking for.
Questions ICANotes Practices Ask
Do I have to leave ICANotes to work with CareVixis?
No. Keeping ICANotes is a supported outcome, not a fallback. CareVixis claims no API integration, certification or partnership with ICANotes, and what is agreed before any commitment is which revenue-cycle data can be obtained and how.
What does ICANotes provide?
ICANotes describes itself as a behavioral health EHR and EMR built exclusively for mental health rather than adapted from a general medical EHR, combining menu-driven documentation with ONC certified charting, integrated billing, telehealth and scheduling.[1]
Is ONC certification the same as payer acceptance?
No. Certification concerns the software's capabilities against a federal programme. Whether a specific claim is paid depends on that payer's medical policy, your contract and the record supporting the service billed. They are different tests, and meeting one says nothing about the other.
Can documentation-driven denials actually be measured?
Yes, and that is the point. Grouped across claims they show a shape: one payer, one service, one clinician, one diagnosis, one time of year. A pattern that specific usually points at a fixable requirement rather than at a clinical failing.
Will CareVixis tell my clinicians how to write notes?
No. Clinical documentation is a clinical responsibility. What CareVixis can do is tell you which payer is denying which service, and what that payer's policy asks for, so any change your clinicians choose to make is aimed at something real.
Keep ICANotes. Add Revenue Intelligence.
Keep your EHR. Keep your clearinghouse. Change what happens after the data comes back.
Free. No obligation. No email required.
Sources
- ICANotes, product overview. Source of the quoted descriptions: "built for mental health, not adapted from a general medical EHR"; "designed exclusively for behavioral health clinicians"; an "ONC Cures Certified platform" offering "ONC-certified charting, integrated billing, telehealth, and scheduling"; a platform that "combines menu-driven documentation with advanced features"; and "Developed by behavioral health professionals", founded 1999. icanotes.com. Accessed 18 September 2026. These are ICANotes' own published descriptions of its product. CareVixis has not independently tested them and makes no claim about them.
- Centers for Medicare & Medicaid Services, Transactions (HIPAA Administrative Simplification), for the remittance advice standard referenced above. cms.gov. Accessed 18 September 2026.
ICANotes publishes efficiency claims of its own. None is repeated here: CareVixis does not restate another company's marketing figures, and publishes no denial rate, recovery rate or revenue increase figure of its own. Nothing on this page states what any payer's medical policy requires; those requirements come from the payer.
Trademarks and non-affiliation
ICANotes® is a trademark of its respective owner and is used here descriptively, to identify software a practice may already use. Quoted product descriptions are ICANotes' own words, cited above.
CareVixis is not affiliated with, endorsed by, sponsored by or certified by ICANotes. No API integration, native integration, certification or partnership with ICANotes is claimed.
Keep the EHR. Add Revenue Visibility Around It.
CareVixis supports practices that want to keep this EHR. VixisIQ™ adds revenue intelligence and VixisTrace™ supports claim root-cause work around the revenue cycle. If a practice later chooses CareVixis-owned technology, the Vixis products can work natively together, but migration is not required.