We just launched a new sleep protocol. See it
The care team that scales
Better outcomes.
More revenue.
Same team.
Most of your patients qualify for care programs their insurance already pays for. HANA finds which ones, coordinates the care every month in 30+ languages, and writes the note. Your clinicians review and sign.
Book a demo →Three ways to run care management.
One of them makes the calls.
One way
Care management software
Mainly used to track time, build the care plan, and assemble the claim. Nothing happens until someone on your team dials.
Another way
Outsourced care management
Based on contracted staff and staffing agencies
- They do the calling. You pay for their hours.
- Capacity capped by whoever they can hire
- Notes handed back to you, not written in your chart
- Under the proposed CY2027 rule, Medicare may not pay you back for them
Our way
AI care coordination
Based on clinician-built protocols
- It dials, it listens, it writes the note
- Every patient, every month, in 30+ languages
- The note lands in your chart, ready to sign
- Not clinical staff, so the proposed CY2027 rule leaves it standing
Your team keeps the relationship, the judgment and the signature. HANA does the dialing.
See it work
See the month actually run.
The loop above is the shape of it. This is a real call going out, the note landing in the chart, and the month ready for your clinician to review and sign.
Proven by the teams running care at scale
Real outcomes, in the words of the operators and clinicians running HANA.
fewer missed
patient calls
“Designed for both Remote Patient Monitoring (RPM) and Remote Therapeutic Monitoring (RTM) programs, enabling scalable, intelligent patient engagement while improving adherence, streamlining clinical operations, and lowering the cost of care.”
“Getting elderly patients ready for surgery over the phone is nearly impossible. HANA reaches them, walks them through everything, and flags whoever still isn't ready so we can step in.”
less time to
respond
“Hana … captures the conversation in structured notes that go straight into the chart, and flags anyone who needs a same-day callback.”
Katie Murphy Psy.D. · Founder of Penryfewer
no-shows
How it works
Forty-five minutes a patient.
We take it under thirty.
One coordinator. Same hours. Two hundred and fifty patients instead of a hundred and fifty.
Hana calls · you set the protocol
It calls from your number until someone picks up. Then medications, symptoms, and what changed.
Hana routes · your team decides
Anything clinical goes to your team, with the reason and the transcript attached.
Your clinician reviews · Hana writes
The note is in the chart before your team opens it. Under that patient, not in a spreadsheet.
You submit · Hana supplies the evidence
Every minute attributed to the person who earned it, ready to attest on the first.
You set the escalation rules. A person on every clinical flag, an audit trail on every call, minutes totalled per patient.
45-60min
per patient, per month, today
What a coordinator spends on one enrolled patient when the calling, the chasing and the note are all done by hand.
120-160
the caseload that caps at
Which is why most programs stall well short of what the panel could support.
29min
what HANA is built for
Same coordinator, same hours, toward 250 patients. HANA makes the calls; your team reviews and attests.
Your team reviews it. Your provider signs it. Nothing is billed until a person on your team approves it.
Have a chat with HANA.
Give us your number. It calls in about ten seconds. Talk to it like a patient would, then let your team try it.
Hear Hana handle a real patient conversation.
Enter your details. Hana texts you to confirm, then calls within seconds, so you can hear it for yourself.
For your clinic
Your team sees four patients. HANA called two hundred.
The care coordination dashboard your team actually works in: who was reached, who needs a person, whose month is documented and ready to bill.
Every call is scored against your protocol. Only the flags surface, each with the call behind it and a named owner.
The note is written the moment the call ends, and the minutes are attributed to whoever earned them. You see what is ready to sign, across every program you run.
Who was flagged, who got it, what they did, when they signed. Any month, any patient, one export.
Builtbyclinicians
Our clinical director still reviews medical necessity for a payer. So every note HANA drafts is written to pass the review it will actually get.
For your patients
The call your patient actually picks up.
Your name on the caller ID, not a number she has been told to ignore. And it works the other way: she rings that number back and HANA answers, any hour, and writes that conversation up too.
Patients rarely leave because the calls stopped. They leave because nobody explained what the program was for, or what it costs them. Every call opens where the last one ended, in her own words, and answers the question that quietly ends most enrollments: what am I paying for this. For a patient whose Medicaid covers the coinsurance, the answer is nothing, and until now nobody had the time to tell her.
30+ languages, switched per patient, same number and same protocol. Nothing to configure, no second line, no interpreter to book. The patients who get a worse call everywhere else get the same call here.
Programs
Every program is a phone call somebody has to make.
Any program where the same patient needs a call next month. CCM, APCM, PCM, BHI and CoCM. Different rules, same phone call. Tap any card to see the steps it runs.
What each program requires and pays

The month is written up before you start your time.
HANA calls the new CPAP patient through the week that decides whether therapy holds, and every call is recorded and summarised straight into the time log. When your clinician opens the patient, the month is already there. The clock they start runs on reading and attesting, not typing.
0:00
Time your team spends writing the month up
4
Documented contacts waiting when they open the chart
Time log · an example month
RTM 98980Mask felt tight. She took it off at 2h 10m.
HANA call · summarised
Top strap loosened a notch. Agreed to try again the same night.
HANA call · summarised
4h 20m. First night above four hours.
Device data · flagged to the threshold you set
5h 05m average across the week. Cadence drops to weekly.
HANA call · summarised
Your clinician's time
Review and attest
4:12
The partnership
You're not buying software. You're getting a partner.
Practices don't quit these programs over the billing rules. They quit over a hundred clicks and a manual nobody had time to read. So we build it with you. Your clinicians set the protocols, we come to you and train your staff, and we stay on it long after you're live.
Your staff do the billable work, under your own NPIs. We never supply the clinician.
A person, not a ticket queue. They take your clinic from the first call to the first billed month, and they are who you ring when something is unclear.
Your onboarding lead
Not a course you have to find time for. Short lessons that land as you reach each step: when you bill chronic care management, what principal care management needs, where behavioral health integration differs. Watchable between patients, with a tutor to ask when a rule is not obvious.
Learn in the gaps
One program, one group of patients, so your team can read the documentation before anything scales. Expand when the numbers hold, not because a contract says so.
Proof before scale
75
years of combined clinical and AI experience45+
care protocols deployedThe staffing model answers this by doing it all for you. If the proposed CY2027 rule is finalized, Medicare stops paying for that.
Defense in depth, on every single call.
Every call opens by telling the patient it's an AI. Behind that sit four layers of protection.
Integrations
It lands in the chart you already use.
Your EHR. Your phone system. Nothing to rip out. The note is written the moment the call ends, attributed to whoever owns the patient.
Questions? Answers.
The things everyone asks.
Not for the programs HANA runs device-free: CCM, APCM and behavioral health integration, where the covered activity is the care-management contact itself. Nothing is shipped, downloaded, or charged to the patient. If your patients already use wearables or connected devices, that device data flows in via API alongside the conversation.
No, and we're deliberate about that. RPM codes (99453/99454/99457) require an FDA-defined medical device that transmits readings automatically. A patient reading a number to us over the phone does not satisfy them, and billing RPM that way is what the DOJ's first RPM False Claims settlement was about. The programs HANA runs are the device-free ones: CCM, APCM, PCM, BHI and CoCM.
No. The opposite. We don't replace the clinician's billable interaction, and HANA's call time is not billed as clinical time. HANA captures the data, drives the adherence, and prepares the documentation so your clinician reviews a flagged worklist and attests, instead of chasing patients.
HANA produces the documentation the codes require; your qualified staff supply and attest to the time. Every interaction is written back as a structured note attributed to a named clinician, across CCM, TCM, APCM, PCM, BHI and CoCM, so the person who bills is the person who did the clinical work, with the record to show it.
Care management software is a co-pilot for your care manager: conversation guides, call summaries, auto-populated care plans, a dialer. Every feature makes a human's call better, and none of them makes the call. HANA does the call itself, then writes the note, so your care manager supervises a panel instead of phoning through a list. A co-pilot makes one person somewhat faster. Removing the dialing is what changes how many patients one person can hold.
You export the month and hand it over. Every check-in stores its transcript and structured note, every care-management minute is attributed to the named clinician who supplied it, every escalation records who received it and what they did, and program consent is captured in the patient's own words on the enrollment call. That's the packet an auditor asks for, assembled as the program runs rather than reconstructed afterwards.
CMS's CY2027 Physician Fee Schedule proposal would pay for RPM and RTM only when the clinical staff furnishing them are direct employees of the billing practitioner or their practice. If it is finalized as written, contracting the calling out to a third-party staffing company stops being billable for those codes from January 1, 2027. HANA fits the model that remains: it is not contracted clinical staff, and its call time is never billed as clinical time. Your own employed clinicians supervise the program, review every flag, and attest the work.
HANA calls patients in 30+ languages, switching automatically per patient. No separate configuration or phone lines required.
Most vendors in this category supply the staff as well as the software, and the CY2027 proposal pays for remote monitoring only when the clinical staff are direct employees of the billing practice. If that is finalized as written, the contracted-staffing model stops being billable for those codes. HANA is the other shape: your own employed clinicians own the patients and the attestation, and HANA is the capacity that makes the calling possible. You can also run us alongside an existing vendor on a different cohort and compare the documentation.
That is the objection the whole program is built around, and it is why onboarding is a named person rather than a login. One owner takes your clinic live, the protocols come pre-built, and the learning is short courses your staff can do in the gaps rather than a manual. The calling itself is the part that consumed the bandwidth, and that is the part HANA does.
No multi-year lock-in. Start on one program and one cohort, keep the documentation either way, and expand when the numbers hold up. If a pilot does not clear the bar you set at the start, you should not be signing anything longer.
Usage-based, per actively managed patient per month, so the cost moves with the panel you actually run rather than with a seat count or a platform tier. We will put the number in front of you on the call, along with the arithmetic against a coordinator's fully loaded cost, because that is the comparison that decides it.
From the blog
How clinics are putting Hana to work.
Why Patient Reminders Don't Reduce Readmissions (And What the Research Actually Shows)
Reminders don't reduce readmissions because readmissions aren't a scheduling problem. Here's the 3-layer engagement model that actually works.
Voice AI in Healthcare Hit Production Scale in 2026. This Is What Actually Changed.
Voice AI in healthcare is no longer a pilot. Here's why 2026 was the tipping point, which use cases deliver real ROI, and what clinic owners should evaluate first.
Why 89% of Healthcare AI Never Reaches Production (And What the 11% Do Differently)
Only 11% of healthcare AI agents reach production. The gap isn't intelligence — it's governance. Here's what the organizations that make it actually do differently.
Ask AI about HANA
Get an unbiased overview from your favorite AI assistant
See it on your own patients.

